Skip to content
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.

Revise the exclusive ordered comparison rules to no longer imply !=V.* #3

Merged
merged 1 commit into from Dec 31, 2014

Conversation

dstufft
Copy link
Member

@dstufft dstufft commented Dec 29, 2014

Instead of having these operators imply a !=V.* this will instead have them more-or-less simply check if the prospective version is greater than or less than the specifier version. They will not however match a post or pre-release of the version mentioned in the specifier unless the specifier itself contains a post or a pre-release. In addition, we will ensure that >V does not match V+local.version even though it is technically greater than V.

In particular that means that something like >1.7 will match 1.7.1 but will not match 1.7.post1 while >1.7.post0 would. Likewise <3.0 would not match 3.0.dev0 while <3.0rc1 would.

This is implemented in pypa/packaging#25

@dstufft dstufft added the PEP440 label Dec 29, 2014
that releases are later than a particular post release, include additional
post releases, by using ``>V.postN``. For example, ``>1.7`` should allow
``1.7.1`` but not ``1.7.0.post1`` and ``>1.7.post2`` should allow ``1.7.1``
and ``1.7.0.post3`` but not ``1.7.0.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

missing the closing ``

@ncoghlan
Copy link
Member

Some minor editorial comments, and an actual error picked up by Marcus, but overall this looks good to me.

I unfortunately renamed the PEP 440 file based on the discussion in issue #2, so that will also need changing in the PR before it will apply cleanly again.

@dstufft
Copy link
Member Author

dstufft commented Dec 29, 2014

This is updated now.

The exclusive ordered comparison ``>V`` **MUST NOT** allow a post-release
of the given version unless ``V`` itself is a post release. You may mandate
that releases are later than a particular post release, including additional
post releases, by using ``>V.postN``. For example, ``>1.7`` should allow
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still another s/should/will/ here.

@ncoghlan
Copy link
Member

Generally looks good to me - just one change that was missed from the previous review, and a realisation that the change log could likely use an introductory paragraph.

@dstufft
Copy link
Member Author

dstufft commented Dec 29, 2014

Updated again.

@ncoghlan
Copy link
Member

Merging this one - I'll also add the 'c'->'rc' normalisation change to the changelog, and then give folks on distutils-sig one last chance to comment before we publish the change on python.org

ncoghlan added a commit that referenced this pull request Dec 31, 2014
Revise the exclusive ordered comparison rules to no longer imply !=V.*
@ncoghlan ncoghlan merged commit 225de0a into pypa:master Dec 31, 2014
@dstufft dstufft deleted the rework-ordered-comparison branch December 31, 2014 02:19
@dstufft
Copy link
Member Author

dstufft commented Dec 31, 2014

At what point can I merge the packaging PR and release it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants