-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3 Update #64
Comments
I think it's a good bug. I haven't been following that direction very much, but I do use tools from here, so getting it updated would be beneficial to me. I haven't started any work in this direction yet, though (other than what's trickled in). |
+1 |
+2 |
So, er, I assume your stuff has just stopped working too? |
Yep, it seems to have. :/ I have entirely too many projects. This one has parts I've used, but can't now. There were a couple of efforts from contributors to move towards an API v3 client, but I haven't seen a pull request, so I should turn my hopes down a bit. Does anyone out there want to help make progress? I certainly use these APIs myself. |
I hope this doesn't come as an unwelcome comment. I saw that @sethwoodworth starred my sigmavirus24/github3.py project which is an attempt at providing an interface to the v3 API. From looking at a bit of your README I would say that mine isn't going to provide an easy transition from your library to mine but there is an (unfortunately incomplete) library copitux/python-github3 which seems to have a similar interface to yours. If anyone starts using mine and finds issues/bugs, a pull request is always welcome. I only have 87% coverage (including calls that require you to authenticate) on tests. The only thing github3.py is missing is the distinction between stargazers and subscribers (watchers). Ian |
With @github's news that they're turning off v2 in a couple of months, are you planning to update this to v3? (Query, rather than passive-aggressive bug. I'm trying to work out if I should start migrating)
The text was updated successfully, but these errors were encountered: