Hi, That's an interesting aspect that I had overlooked and I see how it can be annoying.
Looking at the code, I'm not sure there can be a way to move the data from oauth2client storage to google-auth without spending a lot of time doing so. The two are quite different. A related issue is that the filename for both is the same. At least, as far as I can tell from your backtrace, this doesn't lose the original file. Can you confirm that? It's also a shame that users who upgrade are greeted by a non-descriptive backtrace and no diagnostic due to that. Finally, it seems that the config_folder option is not used anymore here. By the way, have you been able to confirm the migration to google-auth works for you? I wanted to use it with the google account I have through canonical but this actually doesn't work, probably due to company policy (it goes quite far but I get an error during the in-browser authorisation). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078793 Title: gcalcli: uses python3-oauth2client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalcli/+bug/2078793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
