-
Notifications
You must be signed in to change notification settings - Fork 23
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
Use pixi for setting up the dev environment #801
Labels
question
Further information is requested
Comments
I'm in favor of moving things to pixi. This is a nice repo to try things out. It would be great if we could address the following items:
|
Good points. Let's continue under #802 |
Merged
14 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, the contribution guidelines suggest setting up a conda environment based on the
environment.yml
files in the repo. I think there is quite a lot to gain from moving to pixi in the case of glum. In particular:environment.yml
files for different use cases. Pixi has an elegant way of handling multiple environmentsWhat would not change:
conda.recipe/meta.yaml
andconda-mambabuild
, and PyPI builds oncibuildwheel
.I can make a draft PR so we get a better idea how it would look like. What do you think?
The text was updated successfully, but these errors were encountered: