pixi add option that takes in input a Python module name instead of conda package name about pixi

[ruben-arts]

Interesting idea, we are working on improving conda-python mapping thus this data might be available soon. Not sure if this would fit into pixi directly but would be cool to do a prototype!

[traversaro]

Even more futuristic, if cps gets actually adopted by the C++ community, it would be cool to do something similar in C++ with cps package names.

Probably a bit OT, but just to note it somewhere: without going too much in the future with standards that are not even out in alpha, something else quite useful could be a CMake package --> conda package resolver (fyi @AleTarsi).

[ruben-arts]

Ping @wolfv @baszalmstra @nichmor. Do you think this would be easy to add to the pypi-conda mapping tool?

[traversaro]

Probably a bit OT, but just to note it somewhere: without going too much in the future with standards that are not even out in alpha, something else quite useful could be a CMake package --> conda package resolver (fyi @AleTarsi).

Again, a bit OT, but just to past in public a comment in a private chat:

A first pass at the CMake mapping is relatively easy. If a conda package provides a -config.cmake file, then it provides the PackageName. If a conda package provides a -config.cmake file, then it provides all possible packages obtained by varying the cases of packagename, i.e. PackageName, PACKAGENAME, PaCkAgEnAmE, etc etc. For the packages provided by Find.cmake scripts in CMake itself, the simplest solution is just hardcoding. For the packages provided by third-party Find.cmake, the solution is hardcoding ot just ignore them.