[Catalog-sig] Stable-releases-only PyPi
tseaver at palladion.com
Mon Jul 11 18:45:16 CEST 2011
-----BEGIN PGP SIGNED MESSAGE-----
On 07/11/2011 08:41 AM, Éric Araujo wrote:
> Le 10/07/2011 10:11, Tarek Ziadé a écrit :
>> This is not true anymore for metadata 1.2 which follow pep 386.
>> Pypi already implements it. Pushing a non-386 version gets your
>> action rejected.
> I was under the impression that PEP 386 only defined the syntax of
> version numbers and a comparison algo, but no semantics. IOW there
> is no way for a tool to know that 2.6.33 is devel and 2.6.34 stable,
> or that 1.0.4 does not break compatibility with 1.0.2, or anything
> else of the sort.
The PEP386 semantics are implied by the sorting order, where "final"
(non-suffixed) releases sort higher than any suffixed releases except
"post" releases. Any suffix from the 'a|b|c|rc' group implies a
"non-final" / "development" version of some kind (alpha, beta, release
candidate), while suffixes in the 'post' group imply some kind of
patch-level (presumed stable unless re-suffixed with 'dev').
Note that zc.buildout already has a 'prefer-final' option which uses
Tres Seaver +1 540-429-0999 tseaver at palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Catalog-SIG