Martijn Faassen wrote:

To start off, I'm not 100% sure on this, so I'm just checking.

I thought at some stage I had a working windows installation of my software that was using lxml 1.3 binaries (not 1.3.1 or something, just 1.3). When I tried again today it didn't work anymore, and instead had to start using lxml 1.3.4 (for instance).

Is it possible that someone for some reason removed the versions for 1.3 from the cheeseshop? If so, my general recommendation would be never to do this, even if the packages are broken somehow. A release is a release, and people might be depending on it. For this reason, never remove release files, and also never overwrite release files.

Anyway, I'm not at all sure this actually happened with lxml, but I'm just writing this to make sure it won't happen. :)

Thanks for the warning. However, I didn't remove anything myself and I wouldn't know why Sidnei should have. I'm not sure but I have a feeling that we never had any Windows binaries for 1.3... Anyway, I agree that releases should stay where they were uploaded. There are always reasons why you would want to go back to or compare/test with older versions. Note that the "Index of Packages" even lists them all. I actually do that by hand after each release - distutils/PyPI doesn't seem to have a way to say: "don't hide other releases after an upload". Stefan