Comment 38 for bug 686690

Yes, that's what I meant. If python-keyring chooses a non working keyring,
just don't use it at all.

- Martin
On 10/01/2011 9:01 AM, "Benji York" <email address hidden> wrote:
> On Sun, Jan 9, 2011 at 5:49 PM, Martin Pool <email address hidden> wrote:
>> Just catch the gnomekeyring.IOError and assume it means there is no
>> keyring
>
> Unfortunately it's not that easy. The keyring package chooses the back
> end (GNOME keyring in this case) early and doesn't have a mechanism to
> fall back to another back end if the chosen one doesn't end up working.
>
> Oh, I just realized you may be suggesting that launchpadlib (as opposed
> to keyring) catch the exception. Yep, that would be a reasonable
> workaround.
> --
> Benji York
>
> --
> You received this bug notification because you are subscribed to
> launchpadlib .
> https://bugs.launchpad.net/bugs/686690
>
> Title:
> 1.8.0 breaks login_with() API compat with existing credentials files, and
forces keyrings
>