Skip to content

Document arbitrary equality character restrictions in dependency specifiers - #1445

Open
jovial-liu wants to merge 1 commit into
pypa:mainfrom
jovial-liu:docs/arbitrary-equality-grammar
Open

jovial-liu wants to merge 1 commit into
pypa:mainfrom
jovial-liu:docs/arbitrary-equality-grammar

Conversation

@jovial-liu

Copy link
Copy Markdown

A standalone Specifier("===legacy,") preserves the comma, while SpecifierSet("===legacy,") treats it as a separator. Users can therefore get different results when moving an arbitrary-equality version into a dependency specifier.

Document the character set allowed by the dependency specifier grammar, warn that other characters may not work, and demonstrate the comma distinction with an executable example. This follows the documentation direction discussed in #1000 without changing parsing or version semantics.

Validation: all 421 Sphinx doctests passed; the HTML documentation built with -n -W --keep-going without warnings.

Prepared with OpenAI Codex.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant