-
Notifications
You must be signed in to change notification settings - Fork 405
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.6 #469
Comments
It's getting harder to set up a test environment for Python 2.6, but RHEL6 seems to be the main motivation: #477. There have been alternatives available for a few years (http://www.curiousefficiency.org/posts/2015/04/stop-supporting-python26.html) and pip 9 deprecates support for 2.6. |
stennie
added a commit
to stennie/mtools
that referenced
this issue
Sep 14, 2017
stennie
added a commit
that referenced
this issue
Sep 14, 2017
stennie
added a commit
to stennie/mtools
that referenced
this issue
Sep 14, 2017
stennie
added a commit
that referenced
this issue
Sep 14, 2017
stennie
added a commit
to stennie/mtools
that referenced
this issue
Sep 14, 2017
stennie
added a commit
to stennie/mtools
that referenced
this issue
Sep 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Python 2.6.0 was released in 2008, with the final binary release (2.6.6) in Oct 2013. Currently it is retired and thus unsupported.
New tests for mlaunch are written for Python 2.7, and builds are currently failing due to travis-ci testing for 2.6 and 2.7 (PR #468). Note that the tests are passing in 2.7.
I propose removing support for Python 2.6, which is way outdated anyway.
The text was updated successfully, but these errors were encountered: