Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tame the PyPI / Conda mapping chaos #564

@maresb

Description

@maresb

I'm aware of three sources of truth for the correspondence between PyPI and Conda names.

  1. Grayskull's config.yaml. Compact but maintained by hand and incomplete.
  2. The so-called Grayskull PyPI mapping that's not actually used by Grayskull, but is used by conda-lock. This is complete, and uses some cool graph-theoretic heuristics to guess the best mapping. It's also possible to add an override in cases where the result is not as desired. (This might also be used by some parts of the conda-forge infrastructure.)
  3. Prefix-dev's parselmouth. I am aware of its existence but I haven't yet had the chance to look at it in detail.

In order to reduce duplication, it would be nice to consolidate some of these, and especially to uniformize the edge cases. I'm very curious what @nichmor and @mariusvniekerk think.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions