Hi all, github3.py version 0.7.0 was released today. The following is a list of all changes since 0.6.1: - Fix ``Issue.close``, ``Issue.reopen``, and ``Issue.assign``. (Issue #106) - Add ``check_authorization`` to the ``GitHub class`` to cover the `new part of the API http://developer.github.com/v3/oauth/#check-an-authorization`_. - Add ``create_file``, ``update_file``, ``delete_file``, ``iter_contributor_statistics``, ``iter_commit_activity``, ``iter_code_frequency`` and ``weekly_commit_count`` to the ``Repository`` object. - Add ``update`` and ``delete`` methods to the ``Contents`` object. - Add ``is_following`` to the ``User`` object. - Add ``head``, ``base`` parameters to ``Repository.iter_pulls``. - The signature of ``Hook.edit`` has changed since that endpoint has changed as well. See: github/developer.github.com@b95f291a47954154a6a8cd7c2296cdda9b610164 - ``github3.GitHub`` can now be used as a context manager, e.g., :: with github.GitHub() as gh: u = gh.user('sigmavirus24') As of this morning, github3.py is entirely caught up with all recent changes to the GitHub API. Please note that for the new repository statistics API that GitHub attempts to cache the results as much as possible. If they do not have the results cached, though, they will return a 202 and ask that you give them "a moment" to generate (and cache) the results for your request. The documentation for the four new methods explain how github3.py will communicate a 202 to you. Also note that those 202 responses *do* affect your rate limit. Finally, to avoid affecting your rate limit, Repository.update_file, and Repository.delete_file are implemented separately from Contents.update and Contents.delete. I agree there should be only one (obvious) way to do it, but in this case, I feel the versatility of having two is beneficial to you, the developer. Cheers, Ian