Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

fixed cla (theoretically)

CLAs look good, thanks!

@eugenewf Note that the tests are passing on CI, so you don't have any work to do to get Python 3.4 working.

@theacodes Are there any further actions you'd like me to take here? (e.g. with regards to #309 (comment) or #309 (comment))

Apologies for dropping this for so long, I've been rather ill.

I had a conversation with Thea back in February resulting in a recommendation to always explicitly request the scopes if they have been provided. I've written that up and added a failure message for the case where the server only grants some of the scopes requested (which is allowed by the oauth spec). Comments appreciated if anyone thinks there's a better way to handle that case :)