There are at least 2 URI template packages on the PyPI: uritemplate and uritemplate.py. Both of these packages use uritemplate as 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.py because:
uritemplate.py is API-compatible with uritemplate, but the reverse is not true. I have confirmed that this library works with uritemplate.py.- Other projects depend on
uritemplate.py. For example, we are currently working on a project that depends on both github3.py (GitHub API client) and google-api-python-client. Installing both results in an immediate ImportError due to the uritemplate conflict.
This is a simple, low-risk change that would aid compatibility with other projects.
Thoughts?
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?