Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
ATM, more or less all py2 & py3 versions. 99% of all compatibility issues are enconding problems since the string type has changed from byte-string in Py2 to unicode-string in Py3.
Py3 versions started with 3.5 are downward compatible and only in very rare circumstances you will might see any version compatibility problems (I forecast we will see none).
I recommend to drop Py2 support and support all Python versions starting with 3.5.
good point, if version support is clarified we have to add python_requires argument to setup call.
I'm pretty sure there are some instances that still run on py2, so it would be nice to release a final py2 supporting version with a very noticeable deprecation warning (both in the logs and in the release notes) so there's no surprises when we actually deprecate it.
because nobody mentioned it yet, from that link given there is warning
checking setuptools can be done before running setup. but checking if setup file run with pip is harder
other alternative to this method is just check python version before running setup and print warning (or quit) if python version don't meet minimum requirement