On Sep 30, 2015 11:33 AM, "Brett Cannon" wrote:
>
>
>
> On Tue, 29 Sep 2015 at 11:34 Mike O'Driscoll
wrote:
>>
>> Would someone be able to point me to the correct package/developer bring
up/testing instructions.
>>
>> Should I find extra cycles I could
On Tue, 29 Sep 2015 at 11:34 Mike O'Driscoll
wrote:
> Would someone be able to point me to the correct package/developer bring
> up/testing instructions.
>
> Should I find extra cycles I could potentially investigate a fix.
>
>
I think these might be the instructions
I'm completely locked out.
If there is/was a way to add pure username password I'll do that when I can
get back in.
--
Mike O'Driscoll
On Mon, Sep 28, 2015 at 10:57 PM, Glyph Lefkowitz
wrote:
> Mike, do you have another way to authenticate to the site, or are you
>
Would someone be able to point me to the correct package/developer bring
up/testing instructions.
Should I find extra cycles I could potentially investigate a fix.
--
Mike O'Driscoll
On Tue, Sep 29, 2015 at 9:09 AM, Mike O'Driscoll
wrote:
> I'm completely locked out.
If nobody has time to fix the code for OpenID, is there at least an admin with
privileges to associate passwords with people's accounts?
-glyph
> On Sep 29, 2015, at 03:09, Mike O'Driscoll wrote:
>
> I'm completely locked out.
>
> If there is/was a way to add pure
Hello,
I have been unable to login to the PyPi site for nearly a month now via
OpenID (launchpad).
I have the following ticket open but have gotten no traction:
https://bitbucket.org/pypa/pypi/issues/333/unable-to-login-via-openid
Any support would be appreciated.
Thanks,
--
Mike O'Driscoll
Hi Mike,
Sorry, but this is a known problem that no-one has time to investigate or
fix.
Richard
On 29 September 2015 at 01:31, Mike O'Driscoll
wrote:
> Hello,
>
> I have been unable to login to the PyPi site for nearly a month now via
> OpenID (launchpad).
>
> I
Mike, do you have another way to authenticate to the site, or are you locked
out until OpenID works again?
-g
> On Sep 28, 2015, at 14:02, Richard Jones wrote:
>
> Hi Mike,
>
> Sorry, but this is a known problem that no-one has time to investigate or fix.
>
>
>