Skip to content

Drop support for 3.2 #1145

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

Closed
JelleZijlstra opened this issue Apr 6, 2017 · 4 comments
Closed

Drop support for 3.2 #1145

JelleZijlstra opened this issue Apr 6, 2017 · 4 comments

Comments

@JelleZijlstra
Copy link
Member

Typing recently dropped support for Python 3.2 (python/typing#374) and mypy only supports 3.3 and up. Not sure about pytype and PyCharm. The last release of the 3.2 series was in October 2014 and pip and setuptools don't support it.

Concretely, I propose:

  • We stop testing against 3.2 in Travis
  • We don't require 3.2 behavior to be supported in new stubs (e.g., functions added in 3.3 don't need a version_info check).
  • We don't actively remove existing version checks for 3.2. Removing them is fine as part of a larger refactoring.

#1144 is an example of a PR where supporting 3.2 would complicate the stub needlessly.

@gvanrossum
Copy link
Member

gvanrossum commented Apr 6, 2017

Sounds good. I think we should drop 3.2 completely for mypy too.

@gvanrossum
Copy link
Member

We debated this and we will do it for mypy and typeshed.

@gvanrossum
Copy link
Member

Make it so!

@JelleZijlstra
Copy link
Member Author

I can submit the typeshed PR when I get a chance.

gvanrossum pushed a commit that referenced this issue Apr 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants