El 2 Aug 2008, a las 17:45 , Chris Withers escribió:
Benji York wrote:
In case anybody's wondering how this complies with our "no removal of any release whatsoever" policy [1], be assured that a 3.4dev-r73090 thing isn't a release by our standards. This version number not only contains the 'dev' marker, meaning it must have come from a development branch (possibly the trunk), it also contains the -rXXX suffix meaning it was made right from a subversion checkout without having created a tags first (why else would you
want to include the revision number).
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.

This is silly.

Mistakes happen. Buildout and/or setuptools should be tolerant of accidental releases that are then removed from PyPI.

What currently happens in cases like this?

Nothing. It's only a problem if somebody pinned zope.size version to 3.4dev-r73090 in their buildout.cfg. But that's their own fault IMHO because it's clearly not a release._______________________________________________
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to