Transition to parselmouth's PyPI to conda-forge mapping #807
Description
Checklist
- I added a descriptive title
- I searched open requests and couldn't find a duplicate
What is the idea?
Conda-lock's mapping for converting PyPI package names to conda-forge package names is no longer state of the art, and is falling out of maintenance (regro/cf-scripts#3031). I explain the situation with some detailed analysis in conda/grayskull#564. My conclusion there is that we would be better served transitioning to parselmouth.
Why is this needed?
Currently the pypi mapping is not perfect but works in the vast majority of cases to the extent that it doesn't seem to be a major complaint. However, given the lack of maintenance of the mapping, and the observation that many packages seem to be disappearing from it, this will soon come to haunt us if we don't take action.
What should happen?
No response
Additional Context
No response