Please don't remove releases from pypi

[tardyp]

Hello,

It looks like you created toml 0.9.3.1, and removed 0.9.3 from pypi.

pip install -U 'toml==0.9.3'
Collecting toml==0.9.3
  Could not find a version that satisfies the requirement toml==0.9.3 (from versions: 0.6.0, 0.6.5, 0.7.0, 0.7.1, 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.1, 0.9.2, 0.9.3.1)
No matching distribution found for toml==0.9.3

This is problematic as it breaks the CI of people who use things like https://pyup.io/ to manage their dependencies version.

please see example failure:
https://nine.buildbot.net/#/builders/13/builds/1397

[uiri]

Yikes! I'm so sorry. Thank you for bringing this to my attention. PyPI does not permit re-using version numbers either so once it is gone, it is gone; even if I try to upload the same file.

Would releasing a 0.9.4 solve this kind of issue? Or, rather, properly matching the version name in PyPI to the version name I'm using in the code.

[tardyp]

I am afraid it won't help. We already merged an update of requirements, so it is fine now. But for future release, please avoid to reproduce this :)
Thanks for working on toml!

[jwkvam]

@uiri Would you mind cutting a new release? I think it's causing some tools confusion since v0.9.3 is still referenced from setup.py through __init__.py but the available version on pypi is 0.9.3.1 with no 0.9.3 of course.

[technolingo]

It seems releasing 0.9.4 would help in case of Zappa.