At 11:17 AM 6/4/2009 +0200, Tarek Ziadé wrote:
- new PEP 386 | waiting for your feedback
- http://svn.python.org/projects/peps/trunk/pep-0386.txt
From the PEP:
Last ".dev456post623" is a development version of a post-release
This appears incorrect to me; it should be a post-release of a
development version, analagous to ".dev456-r623" in a setuptools version.
I think it would also be helpful to note that one of the new scheme's
design goals is to be a strict subset of the setuptools version
algorithm; you sort of implied it in a couple of places (talking
about the widespread use, and the problem of interpreting such a wide
variety of schemes), but it might be good to point that out, so it's
clear that adopting the scheme for your package will not require
opting out of the setuptools-based infrastructure or depriving anyone
of their preferred tools.
(In that vein, it also might be helpful to suggest that people try
using parse_version() comparisons to verify that their new numbers
are all > their old numbers, if they plan to change schemes. Despite
the strict-subset property, there might be problems in the case where
they are not currently using an equivalent subset.)
- PEP 376 | status : waiting for Phillip complementary feedback (and
anyone else of course)
- up-to-date PEP proposal :
http://bitbucket.org/tarek/pep376/src/tip/docs/pep-0376
- up-to-date prototype code for pkgutil :
http://bitbucket.org/tarek/pep376/src/tip/pkgutil.py
I'll try to look at this again soon, probably the weekend.
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
