-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 these semantics: http://pypi.python.org/pypi/zc.buildout/1.5.2#preferring-final-releases Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAk4bKJwACgkQ+gerLs4ltQ4M4QCeK7p3jzqzuWl3VzZJJ8gyw7+L IM8AoLgr/1+l3tmbpBVBwF9nJKYt+QkD =K3oO -----END PGP SIGNATURE----- _______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
