-
Notifications
You must be signed in to change notification settings - Fork 15
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
Drop support for Python 2.6 #118
Comments
👍 Python 3.2 and 3.3 are also EOL (since 2016-02-27 and 2017-09-29 respectively) and no longer receiving security updates (or any updates) from the core Python team. At least dropping 3.2 is a good thing as it can simplify Unicode handling, and 3.3 generally isn't used much: people using Python 3 have been upgrading more regularly. You can then run https://github.com/asottile/pyupgrade to automatically upgrade syntax for newer versions of the language. |
Thanks for the comment, @hugovk! Yes, I think I will also drop support for Python 3.2 also. This occurred to me when I saw that my
Can you elaborate on this? I'm familiar with the difference in Unicode handling between Python 2 and 3, but not so much about 3.2 and 3.3. |
|
Python 2.6.9 was released 2013-10-29, nearly five years ago, and officially retired Python 2.6.
It's time to drop support for Python 2.6. Other projects are doing the same:
There's a fair amount of Python 2.6 baggage in Scuba:
'{0}'
in string formatting, as opposed to auto-numbering'{}'
compat.check_output
, because Python 2.6 doesn't havesubprocess.check_output()
utils.shlex_split
, because Python 2.6 has a problem with Unicode argumentsunittest.TestCase.assertRaises
gained the ability to be used as a context manager in 2.7.This is a good candidate for the 3.0 milestone.
The text was updated successfully, but these errors were encountered: