Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

switch to pixi #236

Open
aryarm opened this issue Oct 10, 2024 · 0 comments
Open

switch to pixi #236

aryarm opened this issue Oct 10, 2024 · 0 comments

Comments

@aryarm
Copy link
Member

aryarm commented Oct 10, 2024

Once poetry 2.0 is released (hopefully this month?), we could consider switching from conda to pixi!

The benefit of this is that we will be able to move the contents of our dev-env.yml file config into our pyproject.toml file like this. This will also allow us to lock our conda dependencies in a pixi.lock file

The release of poetry 2.0 will make it so that we won't need to duplicate our dependency list as described here

On the user-facing side, everything will be pretty much the same. But on the development side, we will need to adapt our devcontainer.json and GitHub actions to use pixi instead of conda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant