Feature/setup pixi environments - #271
Merged
Merged
Conversation
|
zantDelta
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As suggested by Carles: "Splitsen afhangelijkheiden met pixi features en environments."
Note that this was in place when poetry was used prior DGS_1446 It is currently implemented via optional dependencies, which installs dependencies that are not always needed.
Background: https://pixi.prefix.dev/latest/workspace/multi_environment/#feature-environment-set-definitions
The suggestion by Carles: "Op de .toml moeten ook vaste maximaal python versies gegeven woorden (dus
python >= 3.11, < 3.15als voorbeeld),"is a small improvement which can be added as well