Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!eweka.nl!lightspeed.eweka.nl!193.141.40.65.MISMATCH!npeer.de.kpn-eurorings.net!npeer-ng0.de.kpn-eurorings.net!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-announce-list@python.org Delivered-To: python-announce-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'parameters': 0.04; 'api.': 0.05; 'repository': 0.05; 'cache': 0.07; 'context': 0.07; 'developer.': 0.07; 'see:': 0.07; 'skip:` 10': 0.07; 'e.g.,': 0.09; 'separately': 0.09; 'skip:g 60': 0.09; 'url:github': 0.09; 'api': 0.11; 'changes': 0.15; '(issue': 0.16; '202': 0.16; 'limit,': 0.16; 'limit.': 0.16; 'morning,': 0.16; 'skip:` 30': 0.16; 'to:addr:python-announce-list': 0.16; 'fix': 0.17; 'all,': 0.19; 'finally,': 0.24; 'skip:` 20': 0.24; 'cheers,': 0.24; 'to:2**1': 0.27; 'to:no real name:2**1': 0.29; 'message- id:@mail.gmail.com': 0.30; 'object.': 0.31; 'entirely': 0.33; 'implemented': 0.33; 'agree': 0.35; 'possible.': 0.35; 'case,': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'add': 0.35; 'there': 0.35; 'version': 0.36; 'should': 0.36; 'two': 0.37; 'list': 0.37; 'recent': 0.39; 'explain': 0.39; 'though,': 0.39; 'to:addr:python.org': 0.39; 'changed': 0.39; 'how': 0.40; 'ian': 0.60; 'affect': 0.61; 'today.': 0.61; 'new': 0.61; 'you.': 0.62; 'results': 0.69; 'request.': 0.70; 'beneficial': 0.91; 'responses': 0.93 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=4Wph++GSLwzWZ/uQwlmJhNTZlVKKRvs4LM/bH1dia1w=; b=neekeW4BRheA8VFnXNVce6+CkvVMguC3Kw3AhfO7ja2rkc6AooWq6ZrpyMaDDTypYt 8XMtmm2HEnLrCvp9vXNxNbrQZdzT9qob3poGNChvjKiYm3jt//tfePTuufMPasEDo15M roV2CdVzD+sfqitJWqUDvH7ADVPHd9nEW142lU80yDDUu0+eTU7L/2f5zf1Id9UqCK2O zv6exKI+Dv9IcRU1Iw7O+cqP7ze/PiPyEzVlvC0oekk2vH3QaMDotJu/gItni3IAVajl 4/Hq4svLjoGKN7MRNDH53867NElOhGf9Ez7G9M0n47q/TOsWGy3Pj7LNYUpJ3BMko4hP cLdw== MIME-Version: 1.0 X-Received: by 10.152.115.173 with SMTP id jp13mr26950055lab.49.1368992877463; Sun, 19 May 2013 12:47:57 -0700 (PDT) Date: Sun, 19 May 2013 15:47:57 -0400 Subject: github3.py v0.7.0 From: Ian Cordasco To: github3.py@librelist.com, python-announce-list@python.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Tue, 21 May 2013 11:31:31 +0200 X-BeenThere: python-announce-list@python.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: python-list@python.org List-Id: Announcement-only list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Approved: python-announce-list@python.org Newsgroups: comp.lang.python.announce Message-ID: Lines: 48 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1369128692 news.xs4all.nl 15864 [2001:888:2000:d::a6]:43668 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python.announce:956 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 `_. - 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