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

Use pixi and nox #113

Open
barneydobson opened this issue Mar 25, 2024 · 1 comment
Open

Use pixi and nox #113

barneydobson opened this issue Mar 25, 2024 · 1 comment
Labels
infrastructure Modification or update of tooling for QA, installation, CI or deployment

Comments

@barneydobson
Copy link
Collaborator

@barneydobson @dalonsoa I've used pixi for a while. It's a very exciting up-and-coming project and their road map is great. They are planning to use uv instead of pip which makes it even more exciting. However, it's still in early stages and does not support all use cases. It's definitely something to keep an eye on, though.

My current workflow is using micromamba for development and nox for all other stuff. This requires having two env files: environment.yml for CI testing only, and environment-dev.yml for development purposes. I usually put them under a folder called ci/requirements. So, for development purposes, the command becomes:

micromamba env create -f ci/requirements/environment-dev.yml
micromamba activate env_name

Then, testing, linting, and type checking becomes just running:

nox

Originally posted by @cheginit in #107 (comment)

@barneydobson barneydobson mentioned this issue Mar 25, 2024
6 tasks
@barneydobson barneydobson added the infrastructure Modification or update of tooling for QA, installation, CI or deployment label Mar 25, 2024
@cheginit
Copy link
Collaborator

Pixi is finally adding support for pyproject.toml! Check out the issue here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Modification or update of tooling for QA, installation, CI or deployment
Projects
None yet
Development

No branches or pull requests

2 participants