If NO_GCE_CHECK is True we avoid checking for a GCE environment  (_detect_gce_environment is not executed)

Pull recent auth2client release (crypt + timeout)

Following @craigcitro's suggestion

Backward compatibility update (Google/oauth2client)

Use '==' or '!=' instead of 'is' or 'is not'.

Avoid GCE checking if NO_GCE_CHECK is True

…rectServer and ClientRedirect classes

Fixes #125.

NOTE: '%s.%s' does not behave the same between versions and should
      be removed throughout this library.

I will be following this up with a set of regression tests (hopefully
some of which will fail) and we can assess the damage of other uses
of '%s'.

Fixing JSON key service account assertions in Python3.

It turns out that the result may be different depending on openSSL versions;
rather than play games, we just check that we get one of the expected outputs.

New crypt function test fails with system python2.6 on OSX

…S or ENOLCK

This forces `util.positional` to correctly wrap the function it produces, in
particular to fix an issue with generation of docstrings. This also cleans up
the docstrings for `tools.run_flow` and `old_run.run` to be valid restructured
text.

Fixes #124.

Add functools.wraps() to util.positional().

Previously, we always tried to grab the *most* recent SDK version for building
docs; this change loosens this, to grab the most-recent-and-readable version.

Be more permissive about GAE SDK versions.

Both print() and format() are compatible from 2.6. Also, format() is much nicer to use for internationalization since you can define the location of your substitutions. It works similarly to Java and .net's format() as well. Great stuff!

Should I tackle the other examples as well, or is piece meal all right?

Use assert_called_once_with, which exists, instead of
assert_called_exactly_once_with, which does not exist.

This makes two changes:

* Force `tox` to use a new version of `sphinx`, since we depend on features
  from the `1.3` branch.

* Tweak the `build-docs` script to build on any push. The logic for skipping
  the build in the case of a non-master push was originally in place to
  prevent new docs from being pushed live, but we opted to make that manual
  instead. As a result, this just masks docs errors in pull requests.

Adds support for Google Developer Shell session credentials

According to the [OAuth2
docs](https://developers.google.com/accounts/docs/OAuth2WebServer#tokenrevoke),
we can use either the refresh token or access token when revoking a token. If
we've lost the refresh token for some reason, we should fall back to revoking
via access token. (Note that if the access token has expired, this will still
raise, which is the correct behavior.)

Fixes #132.

Fall back to using an access_token for revocation.

Release v1.4.7.