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
On Sun, Jan 9, 2011 at 5:49 PM, Martin Pool <email address hidden> wrote: IOError and assume it means there is no
> Just catch the gnomekeyring.
> 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