Conda-forge package and Pypi package with the same name

[boisgera]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

The sequence of shell commands that fails:

pixi init
pixi add python
pixi add pandoc
pixi add --pypi pandoc
pixi run python -c "import pandoc"

Issue description

A corner case of hybrid projects needing a conda-forge package with a name and a different pypi package with the same name.
Here: pandoc refers on conda-forge to the Haskell CLI/library and pandoc on Pypi refers to (one of the) corresponding Python library. "Pandoc-the-Python-library" requires "Pandoc-the-Haskell-tool" to be installed.

Note that the following alternate sequence of commands works (but I'd rather not use it since the pandoc pypi dependency is not recorded in the pyproject.toml file):

pixi init
pixi add python
pixi add pandoc
pixi add pip
pixi run pip install pandoc
pixi run python -c "import pandoc"

Expected behavior

Expected behavior : the last line "should" work ; the Python pandoc module should be importable in the pixi environment defined by the previous commands.

pixi init
pixi add python
pixi add pandoc
pixi add --pypi pandoc
pixi run python -c "import pandoc"

[ruben-arts]

This is indeed a bug. IIRC, the verify_pypi_platform_satisfiability is not looking at the correct info. It should take into account the purls.

Thanks for reporting!

[ruben-arts]

This is fixed in #888

[ruben-arts]

This is also the case for libclang

[ruben-arts]

This is unfortunately reopened with v0.19.1 as we broke some environments with the logic we implemented in v0.19.0. We're working on a proper fix right now so again fix this issue but in a v0.19.2 release.