× Unable to solve pypi dependencies for the dev311 environment because no compatible python interpreter can be installed for the current
│ platform
...
help: Try converting your [pypi-dependencies] to conda [dependencies]
Using Pixi 0.34.0 on a MacOS ARM machine.
Issue description
I'm aware of the error message provided. It is related to https://github.com/prefix-dev/pixi/issues/1051, and I understand the reasons behind it. I do not understand why this error appeared in this example, since I attempted to avoid using any PyPi dependencies.
From my understanding, any dependencies specified in project.dependencies will normally be treated as PyPi dependencies under the default feature. But based on the docs in https://pixi.sh/latest/advanced/pyproject_toml/#dependency-section, I expected that respecifying Numpy in tool.pixi.dependencies would override the requirement. But checking pixi info, I see:
Numpy as specified as both a PyPi and Conda dependency. If I were to comment out the dev311 environment and run pixi install, I see that Pixi attempts to solve for PyPi deps, but the resulting lockfile doesn't contain any.
Is this a bug, or is there an edge case or scenario that I'm not considering where this makes sense? If so, is there a way to explicitly ignore the project dependencies, or should I just use a pixi.toml?
Expected behavior
My expectation is that Numpy would not be considered a PyPi dependency when running pixi info, and that the original Pixi configuration would solve on my existing system on Pixi 0.34.0
Checks
[x] I have checked that this issue has not already been reported.
[x] I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
I'm working with the following Pixi configuration
This unexpectedly raises the error:
Using Pixi 0.34.0 on a MacOS ARM machine.
Issue description
I'm aware of the error message provided. It is related to https://github.com/prefix-dev/pixi/issues/1051, and I understand the reasons behind it. I do not understand why this error appeared in this example, since I attempted to avoid using any PyPi dependencies.
From my understanding, any dependencies specified in
project.dependencies
will normally be treated as PyPi dependencies under the default feature. But based on the docs in https://pixi.sh/latest/advanced/pyproject_toml/#dependency-section, I expected that respecifying Numpy intool.pixi.dependencies
would override the requirement. But checkingpixi info
, I see:Numpy as specified as both a PyPi and Conda dependency. If I were to comment out the
dev311
environment and runpixi install
, I see that Pixi attempts to solve for PyPi deps, but the resulting lockfile doesn't contain any.Is this a bug, or is there an edge case or scenario that I'm not considering where this makes sense? If so, is there a way to explicitly ignore the project dependencies, or should I just use a
pixi.toml
?Expected behavior
My expectation is that Numpy would not be considered a PyPi dependency when running
pixi info
, and that the original Pixi configuration would solve on my existing system on Pixi 0.34.0