DRY way to deal with multi environments?

[mforbes]

For testing, I would like to have multi environments, but I don't see a DRY way to do this:

# pixi.toml
[workspace]
channels = ["conda-forge"]
platforms = ["osx-arm64", "linux-64", "osx-64"]

[feature.py39.dependencies]
python = "~=3.9.0"
[feature.py310.dependencies]
python = "~=3.10.0"
[feature.py311.dependencies]
python = "~=3.11.0"
[feature.py312.dependencies]
python = "~=3.12.0"
[feature.py313.dependencies]
python = "~=3.13.0"
[feature.py314.dependencies]
python = "~=3.14.0"

[environments]
py39 = ["py39"]
py310 = ["py310"]
py311 = ["py311"]
py312 = ["py312"]
py313 = ["py313"]
py314 = ["py314"]

test39 = ["test", "py39"]
test310 = ["test", "py310"]
test311 = ["test", "py311"]
test312 = ["test", "py312"]
test313 = ["test", "py313"]
test314 = ["test", "py314"]
... 

Am I missing something? Is there a simpler approach?

[pratikrath126]

Hey! I see the pain - this is pretty verbose. The usual pattern in pixi is to put common deps in [dependencies] and use features only for the parts that change. You could also treat each py3x feature as its own environment and skip the wrapper envs unless you need extra combinations. Something like:

[feature.py39.dependencies]
python = '~=3.9.0'

[feature.py310.dependencies]
python = '~=3.10.0'

[environments]
py39 = ['py39']
py310 = ['py310']

That cuts out the middlemen. If you really need the test* combos, you might be stuck with the repetition. Pixi prioritizes explicit envs over DRY trickery. Hope that helps!

[mforbes]

Thanks @pratikrath126. I am not sure if I am missing something, but I don't see how your suggestion is any different from what I am actually doing. What "wrapper" envs are you skipping? Just the tests? I need those for CI. If I am not missing anything, then I guess I will just have to write an update script the defines the environment matrix. I will post back here when I get something working.