Closed nsylv closed 5 years ago
Currently, the Python version is specified in 3 places:
1) README badge
2) PyPI page in the Classifiers
section
3) .travis.yml / Travis CI tests
1 & 2 are both derived from the classifiers
specified in setup.py and are the canonical answer for what we have committed to and should be supporting.
3 is what versions of Python we actually test.
We don't foresee any cases where those 3 shouldn't be the same, but maybe for test perf we might not test against a specific Python version if other tests against previous/later versions give us confidence that that specific version will work (e.g. if tests pass for 3.4 and 3.6, I don't think we need to test 3.5).
We could add a "Requirements" section to the installation instructions specifying the compatible Python versions to make it more visible.
pip install tamr-unify-client
from installing tamr-unify-client
on incompatible Python versions. NOTE: this only affects version 0.3.0 and newer. E.g. trying to pip install tamr-unify-client
from Python2.7 will result in tamr-unify-client
version 0.2.0 being installed.
Got the following error after running the quickstart example in the docs:
The issue is that I'm running python 2.7, but 3.6+ is required. Maybe we could add a requirements section to the docs and github to help make this more visible?