PEP 386 and post-releases
In re-reading PEP 386, I noticed that the "Version Specifiers" section explicitly excludes post releases like "2.5.post1" or "2.5.1.post1" from matching a request for "2.5". I can understand excluding all pre-releases from a general request like "2.5", but why exclude post releases? Aren't those intended to fix minor release issues that don't warrant a version number bump? As in, if I have a choice between "2.5", "2.5.post1" and "2.5.post2", isn't "2.5.post2" going to be the one I want, rather than "2.5"? Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Sunday, February 3, 2013 at 12:43 AM, Nick Coghlan wrote:
In re-reading PEP 386, I noticed that the "Version Specifiers" section explicitly excludes post releases like "2.5.post1" or "2.5.1.post1" from matching a request for "2.5". I can understand excluding all pre-releases from a general request like "2.5", but why exclude post releases? Aren't those intended to fix minor release issues that don't warrant a version number bump? As in, if I have a choice between "2.5", "2.5.post1" and "2.5.post2", isn't "2.5.post2" going to be the one I want, rather than "2.5"?
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com (mailto:ncoghlan@gmail.com) | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org (mailto:Distutils-SIG@python.org) http://mail.python.org/mailman/listinfo/distutils-sig
I agree with this understanding fwiw. Makes sense to me.
participants (2)
-
Donald Stufft
-
Nick Coghlan