Just a follow up. On Jan 26, 2014, at 4:40 PM, Richard Jones <richard@python.org> wrote:
It definitely looks like we've got some issues introduced in recent server migrations and reconfigurations. Things I'm aware of:
- OAuth is busted - OpenID is confused and/or busted
These two issues existed prior to the migration as far as I can tell.
- password reset is possibly busted
This has been fixed.
- pypissh is busted
This is still the case and was known from the first announcement. Additionally it seems there is an issue with the health checks when connecting from Australia that cause issues where folks will intermittently get the static page instead of the real PyPI.
Richard
On 27 January 2014 00:26, Alex Clark <aclark@aclark.net> wrote: On 1/25/14, 6:38 PM, Donald Stufft wrote: My question to you is, is this something that distutils-sig is willing to have happen? If we are to re-enable pypissh we’ll need to write a new solution to doing it that can be properly HA’d and we’d prefer to put our efforts into improving things for a much larger set of people.
+0 re: pypissh, but I am still interested in seeing OAuth support come back:
- https://bitbucket.org/pypa/pypi/issue/85/oauth-authorise-not-found-https-mus...
Any idea if this can come back as part of PyPI or if we have to wait for warehouse? Nice work on the infrastructure, thank you!
-- Alex Clark · http://about.me/alex.clark
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA