Motivating example, pydantic-ai-slim: https://conda-mapping.prefix.dev/pypi-to-conda-v1/conda-forge/pydantic-ai-slim.json
The earliest pypi version of this package is 0.0.6. However, conda-forge didn't start building it until 0.2.14. This means that earlier versions of parselmouth fallback to other heuristics and suggest the pydantic package.
This incorrect mapping happens for cases where conda-forge built later, or when the conda-forge releases are more sparse than the pydantic ones.
The expected behavior ought to be that missing versions do not trigger a fallback to another package as a general rule. There might be a case to be made if a different conda package name carries over as a spiritual successor for a pypi package, but I don't know of any of those cases
Motivating example,
pydantic-ai-slim: https://conda-mapping.prefix.dev/pypi-to-conda-v1/conda-forge/pydantic-ai-slim.jsonThe earliest pypi version of this package is 0.0.6. However, conda-forge didn't start building it until 0.2.14. This means that earlier versions of parselmouth fallback to other heuristics and suggest the
pydanticpackage.This incorrect mapping happens for cases where conda-forge built later, or when the conda-forge releases are more sparse than the pydantic ones.
The expected behavior ought to be that missing versions do not trigger a fallback to another package as a general rule. There might be a case to be made if a different conda package name carries over as a spiritual successor for a pypi package, but I don't know of any of those cases