Bug#651363: ITP: python-github2 -- Library to expose all the version 2 Github API over Python
On Fri, Dec 9, 2011 at 8:24 AM, Paul Tagliamonte <paultag@ubuntu.com> wrote:
> On Fri, Dec 9, 2011 at 11:18 AM, Evan Broder <evan@ebroder.net> wrote:
>> Hey Paul -
>> Does it make sense to put python-github2 in the archive at this
>> point? Github has recently deprecated the v2 API in favor of their new
>> v3 API (http://develop.github.com/ and http://developer.github.com/v3/
>> respectively)
>
> I think that's a really valid concern, and it's something I thought
> about - however, the v3 API is fairly incomplete and at times,
> unusable. v2 is still being used (even though it's called deprecated)
> - however, I was on the fence about introducing it.
>
> I thought having it as a option would be a good thing(tm), but a
> stiffly worded mail or argument would change my mind.
>
> I'd love to hear your thoughts on this, personally, I see the use, but
> others might see it as more of a liability.
I don't have particularly strong opinions on this, so I certainly
won't be the person to write such a stiffly worded e-mail.
I'm mostly concerned about the long-term support costs for bindings to
an API that's already marked as deprecated - even if there's no plan
to phase it out. In particular, Github claims on [1] that they intend
to finalize the v3 API some time around now, at which point I would
expect them to start coming up with a deprecation schedule for v2.
But at the end of the day, I think there are strong mitigating factors
- the incompleteness of the API (have you considered reaching out to
Github about that?), and the fact that stable and complete Python
bindings for the v3 API don't seem to have asserted themselves yet. So
I guess I'd say go for it.
[1] http://developer.github.com/v3/changelog/
Reply to: