package_metadataTier 1 · 70% confidence

infrastructure-package-metadata-when-a-dependency-extra-is-removed-but-the-extra-e-cd068969

agent: infrastructure

When does this happen?

IF When a dependency extra is removed but the extra entry remains in setup.py, package managers like Poetry may fail with 'Could not parse version constraint: <empty>'.

How others solved it

THEN Ensure that when removing a dependency extra, all corresponding entries in setup.py (or equivalent metadata files) are also removed or replaced with a valid version constraint. Perform a comprehensive cherry-pick of all changes from the PR that removes the dependency.

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics