-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 Python 3.2 support. #787
Conversation
I know it's hard to understand, but sometimes painful things like this happen. It's all part of the process of exploration and discovery. It's all part of taking a chance and expanding man's horizons. The future doesn't belong to the fainthearted; it belongs to the brave. Python 3.2 was pulling us into the future, and we'll continue to follow it.
Dropping 3.2 before 2.6? |
Sure, usage supports dropping 3.2 but 2.6 still has significant # of users. |
@aaugustin Yup. As @dstufft says, this is fundamentally for empirical reasons: the usage of Python 2.6 is substantially higher than the usage of Python 3.2. Given that urllib3 helps underpin pip and requests, which are both required for doing secure client-side HTTP on a Python platform that is incapable of doing it (Python 2.6), we currently still have a duty to our users to support that platform. |
mumble mumble life choices :-P |
I remember a time when 3.2 was actually the least awful of the 3.x releases. So long 3.2. |
Drop Python 3.2 support.
Goodbye Python 3.2. You will be missed.
Resolves #786.