This commit is contained in:
2025-04-12 22:23:50 +02:00
parent c20ead3737
commit 042a6e513f

View File

@ -1,6 +1,6 @@
# TODO # TODO
- [ ] ## Make envs available in jupytera - [x] ## Make envs available in jupytera
There's [pixi-kernel](https://github.com/renan-r-santos/pixi-kernel) but it is specifically "per directory", which does not fit our use case. There's [pixi-kernel](https://github.com/renan-r-santos/pixi-kernel) but it is specifically "per directory", which does not fit our use case.
@ -16,6 +16,8 @@ The only "problem" is in how jupyter shows the env names:
Note: if the `envs` folder is called differently, no prefix is shown at all... This might be an alternative idea. Note: if the `envs` folder is called differently, no prefix is shown at all... This might be an alternative idea.
**Solution**: setup.sh creates/updates the symlink as part of the procedure.
- [ ] ## Shared features - [ ] ## Shared features
Pixi supports "features" (i.e., sets of packages that allow the user to do XYZ). This would be very useful for, e.g., a feature like "be able to plot on jupytera", which gives the correct versions of ipympl, matplotlib, etc. Pixi supports "features" (i.e., sets of packages that allow the user to do XYZ). This would be very useful for, e.g., a feature like "be able to plot on jupytera", which gives the correct versions of ipympl, matplotlib, etc.