Skip to content

Trying to understand "package-only-prereleases-boundary" scenario #161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
notatallshaw opened this issue Mar 16, 2024 · 1 comment
Closed

Comments

@notatallshaw
Copy link

This is the scenario: https://github.com/astral-sh/packse/blob/0.3.12/scenarios/prereleases.json#L520

In this scenario package a only has prereleases, but the specifier used is an exclusive specificier a<0.2.0, the spec says:

The exclusive ordered comparison <V MUST NOT allow a pre-release of the specified version unless the specified version is itself a pre-release. Allowing pre-releases that are earlier than, but not equal to a specific pre-release may be accomplished by using <V.rc1 or similar.

Now, I appreciate there are other parts of the spec that may be contradictory. So I'm not sure if this is an intentional design choice or not? But my understanding is the intent of the spec is it should not be allowed: pypa/packaging#776 (comment)

@notatallshaw
Copy link
Author

Pre-releases really need a new PEP to overhaul the language, and packse isn't well aligned with the current spec anyway, for the reasons outlines here: #171 (comment)

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

No branches or pull requests

1 participant