-
Notifications
You must be signed in to change notification settings - Fork 19
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
remove support for Python 2.7, 3.5, 3.6 #70
Comments
As of commit 9ee3f96, support for Python 2.7 has been removed, and also support for Python 3.5 and 3.6 has been removed. For motivation, please read the commit messages on branch |
I strongly support this. I think that it can be done without much more discussion. Actually the same for Tulip. I am now a "member of industry" and I can confirm that Python 2.7 is not for new development and mostly survives only where it is deeply embedded in a product, etc. As for versions of Python 3, I agree with following NumPy. If users have difficulties because of requirements of 3.6, we can discuss or patch as needed. To be explicit, 3.5 is past end-of-life, but 3.6 is scheduled to continue to receive security updates until end of this year. |
Is there any reason not to make the same changes in https://github.com/tulip-control/tulip-control/ ? |
I think it would be fine to move to 3.7+ for tulip-control. |
Thank you for the comments, I merged the changes from branch I do not know of any reason why to not make the same changes to A relevant change is to pass the parameter This defines the metadata field For Including Relevant resources:
The documentation at:
Also, I removed the Python 2 Trove classifiers, but did not add the classifier "Programming Language :: Python :: 3 :: Only", because I am not sure what the convention is, because Regarding Python 3.10 support, I created a branch |
I have now changed So this issue appears to have been addressed. Regarding CI testing with Python 3.10 (mentioned above: #70 (comment)), this can be revisited after Python 3.10 has been released and wheels for Line 22 in a23ddcf
so |
This issue has been addressed as of commit beadd12. About the branch pip install -U --only-binary=":all:" --python-version="3.9" --target=/tmp/foo numpy scipy (The arguments Installation did complete without errors in Python 3.10, but when I
The module that was not found is an extension module, namely |
Python 2.7 development has completely stopped. The Python ecosystem has now moved to Python 3. Most major packages have ceased support for Python 2.7, for example
numpy
did so about 2 years ago (numpy == 1.17.0
). So it is time to remove support for Python 2.7 frompolytope
. It suffices to remove 2.7 from the supported Python versions, pass the parameterpython_requires
to the functionsetuptools.setup
, and use features available on Python 3, and in newer versions of dependencies where needed.This change is motivated by the benefits of using the function
numpy.random.default_rng
that is available in newer versions ofnumpy
. There is no reason to constrainpolytope
's code to remain compatible with Python 2.7, and thus not use new functionality available in recent versions of dependencies.The text was updated successfully, but these errors were encountered: