On Sat, Aug 02, 2008 at 05:23:14PM -0400, Fred Drake wrote:
On Sat, Aug 2, 2008 at 9:27 AM, Benji York <benji@zope.com> wrote:
Still, it's likely that someone was using it and their buildouts are now broken. We should have instead generated a proper release with a higher version number and left the dev release alone.
Yes.
It would be even better if PyPI refused registrations of dev versions.
That would be good. What I don't understand about this thread is why 3.4dev was "newer" than 3.4.0. Doesn't PyPi use the same versioning rules as setuptools? $ python Python 2.5.2 (r252:60911, Jul 20 2008, 01:20:16) [GCC 4.1.2 (Gentoo 4.1.2 p1.1)] on linux2 Type "help", "copyright", "credits" or "license" for more information. f>>> from pkg_resources import parse_version
parse_version('3.4dev-r73090') < parse_version('3.4.0') True
So what exactly was the problem? -- Paul Winkler http://www.slinkp.com