Feature/optional dependencies should be pinned in pixi.toml

[redeboer]

Imagine the following setup:

pixi init
pixi add 'python==3.11.*'
pixi add mypy --feature dev

[project]
name = "pixi-test"
version = "0.1.0"
channels = ["conda-forge"]
platforms = ["linux-64"]

[dependencies]
python = "3.11.*"

[feature.dev.dependencies]
mypy = ">=0.812,<1.10"

Similar to Cargo.lock, I expect the exact mypy version to be listed in pixi.toml as well, but it isn't:

grep mypy pixi.lock

Is this a design choice? For instance, (in PyPI lingo) is pixi.lock considered to be a list of requirements or a list of constraints?

[bollwyvl]

In my understanding, a feature won't impact the lockfile until it is explicitly composed into an environment:

[environments]
dev = {features = ["dev"]}

[redeboer]

Thanks, that seems to work yes. Perhaps that does make the case for adding a flag that defines environments for each new feature, as discussed in #1221 (comment), a bit stronger then.