Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm trying out using Pixi for managing our Conda and Pypi environment in place of Mamba.
pixi-kernel replaces nb-conda-kernels to allow us to support per-project environments.
I'm using features to capture each tutorial, then adding the tutorial feature to the default environment. The
[dependencies]
table captures our base dependencies, though we might want to refactor them out into features as well ('jupyterlab support', 'cli', 'storage', 'fast xarray',...).You can test the lab locally with either
pixi run lab
ordocker compose up py
.There is one little oddity I know of right now in the pixi workflow. If you create a new directory ((like a project),
pixi init
, then following pixi commands don't target that manifest as normal.This is because the image has already set a
pixi shell
(wellpixi shell-hook
) to force pixi to look for a specific manifest and recorded that in an environment variable. Pixi will warn that it's using a different manifest, but its easy to screw that up.Running
pixi shell --manifest-path ./pixi.toml
will set the pixi scope to the current environment.