Switch from "uritemplate" to "uritemplate.py" #57
Comments
|
+1 We are having the same issue of incompatibility between the 'github3.py' and 'google-api-python-client' libraries. Switching this project over to using |
|
Even though the technical aspect of the change sounds very simple I'd like to know more before welcoming a pull request welcoming the change. This smells like a political problem, like an unclean fork. What's being done upstream between uritemplate and uritemplate.py to resolve the problem? |
|
Any update on this issue? Discogs is trying to use this client for the YouTube v3 API but we are running into this same error. |
|
This hasn't gone away. As to the upstream, it seems that uritemplate.py claims API compatibility with uritemplate which hasn't had an update since Aug 27, 2013. While it may be a political issue the effect is very real, running an ansible playbook that needs to talk to google cloud and github at the same time is... challenging |
|
For folks subscribed to this issue but not otherwise watching the project: #146 just went by and I didn't realize during its review that this issue was opened on the matter. Has this issue budged at all in the last few months? I see recent commits over at https://github.com/uri-templates/uritemplate-py/commits/master including one by @graingert. |
|
For everyone affected by this issue: has anyone ever bothered to contact the maintainers of both libraries and simply ask what's up? It's been nearly three years since either of them cut a release; I wonder if they can be merged and the whole problem solved properly. |
As of uritemplate 3.0.0 and uritemplate.py 3.0.2, the two packages are equivalent. There were no changes to functionality; see https://github.com/sigmavirus24/uritemplate/blob/master/HISTORY.rst.
There are at least 2 URI template packages on the PyPI: uritemplate and uritemplate.py. Both of these packages use
uritemplateas the package name to be imported, which causes a conflict when both are installed (see python-hyper/uritemplate#14).I propose that this project depend on
uritemplate.pybecause:uritemplate.pyis API-compatible withuritemplate, but the reverse is not true. I have confirmed that this library works with uritemplate.py.uritemplate.py. For example, we are currently working on a project that depends on bothgithub3.py(GitHub API client) andgoogle-api-python-client. Installing both results in an immediateImportErrordue to theuritemplateconflict.This is a simple, low-risk change that would aid compatibility with other projects.
Thoughts?
The text was updated successfully, but these errors were encountered: