Hey all, As anyone here who has uploaded anything to PyPI recently is aware of, PyPI's uploading routine has been in a semi broken state for awhile now. It will regularly raise a 500 error (but will often still record the release, but sometimes only a partial release). Well, the good news is, that Warehouse's upload routines should generally be good enough to use now. This will be more or less the same as if you uploaded to PyPI itself (they share a backing data store) but hitting the newer, better code base instead of the slowly decaying legacy code base. You can upload via Warehouse by editing your ~/.pypirc file and making it look something like this: [distutils] index-servers = pypi warehouse [pypi] username:<username> password:<password> [warehouse] repository:https://upload.pypi.io/legacy/ username:<username> password:<password> Alternatively, you can ditch the [warehouse] section, and just totally switch over to this by doing: [distutils] index-servers = pypi [pypi] repository:https://upload.pypi.io/legacy/ username:<username> password:<password> Then you can upload using ``twine upload -r warehouse dist/*`` or ``twine upload dist/*`` based upon which of the above options you picked. This code is not as battle tested as PyPI itself is, so if you run into any bugs please file an issue with https://github.com/pypa/warehouse. This code should generally give a successful response all of the time (given the upload itself was good) and properly utilizes database transactions so that it should completely eliminate the cases where you get a partial upload. Hopefully this will help solve some of the problems folks are having with PyPI in the interim before we can completely switch over to Warehouse. — Donald Stufft
Op 05/06/16 om 15:42 schreef Donald Stufft:
Hey all,
As anyone here who has uploaded anything to PyPI recently is aware of, PyPI's uploading routine has been in a semi broken state for awhile now. It will regularly raise a 500 error (but will often still record the release, but sometimes only a partial release).
Well, the good news is, that Warehouse's upload routines should generally be good enough to use now. This will be more or less the same as if you uploaded to PyPI itself (they share a backing data store) but hitting the newer, better code base instead of the slowly decaying legacy code base.
I had problems uploading to PyPI recently, getting an error although the upload seemed to have gone fine in reality. I did 8 uploads of Plone packages today using the warehouse url. All have gone fine. Thanks a lot, Donald! -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl
On 2016-06-12 01:48:40 +0200 (+0200), Maurits van Rees wrote: [...]
I had problems uploading to PyPI recently, getting an error although the upload seemed to have gone fine in reality. I did 8 uploads of Plone packages today using the warehouse url. All have gone fine.
Thanks a lot, Donald!
Agreed. I switched OpenStack's release upload automation to hit Warehouse a week ago. Before that we were frequently getting HTTP 500 errors uploading releases of our various projects directly to PyPI, and (aside from one day last week where a PyPI denial of service attack was impacting uploads) the transition has very gone smoothly (some 50+ releases so far). Thrilled to see Warehouse coming along! -- Jeremy Stanley
participants (3)
-
Donald Stufft
-
Jeremy Stanley
-
Maurits van Rees