Benji York wrote:
>> In case anybody's wondering how this complies with our "no removal of any
>> release whatsoever" policy , 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?
Simplistix - Content Management, Zope & Python Consulting