Should be able to retry failed file uploads

[ewdurbin]

Originally reported by: Toby Roseman (Bitbucket: tobyroseman, GitHub: tobyroseman)

---

Here is the sequence of events:

• I tried to upload a wheel to PyPI using twine
• The upload failed. I got the following error: "HTTPError: 503 Server Error: backend read error"
• I tried it again. I got the following error: "HTTPError: 400 Client Error: A file named "GraphLab_Create-1.5-cp27-none-macosx_10_5_x86_64.macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl" already exists for GraphLab-Create-1.5. To fix problems with that file you should create a new release."
• At this point I decided to delete the release from PyPI
• After trying to upload again, I get the following error: HTTPError: 400 Client Error: This filename has previously been used, you should use a different version.

I think there are two problem here:
#1 - If an upload fails because of a server error, you should be able to try it again.
#2 - If you delete a release, you should be able to create it again.

---

• Bitbucket: https://bitbucket.org/pypa/pypi/issue/306

[ewdurbin]

Original comment by Toby Roseman (Bitbucket: tobyroseman, GitHub: tobyroseman):

---

In order to get my change uploaded. I had to bump the version number and upload it again.

[ewdurbin]

Original comment by Martin Alderete (Bitbucket: malderete, GitHub: malderete):

---

+1 for these 2 user cases. Thanks in advance!

[ewdurbin]

Original comment by Wolfgang Maier (Bitbucket: wm75, GitHub: wm75):

---

I agree with you that if an upload fails you should be able to retry it.

I do not agree on your point 2 though. Just because you delete a release that does not mean someone else hasn't downloaded it already, in which case the version number would become ambiguous.

[ewdurbin]

Original comment by Mike Fletcher (Bitbucket: mcfletch, GitHub: mcfletch):

---

Can I suggest that use case 2 (delete a release and redo the whole process) is a strong requirement on the testpypi server?

The test pypi server's whole point is to allow people to test their releases before committing them to the main server. With the policy as it stands you have to bump versions just to test and see if the packaging is working.

[di]

Essentially a duplicate of pypi/warehouse#726.