-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Drop Python 3.2 support. #3244
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
Merged
Drop Python 3.2 support. #3244
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -514,3 +514,64 @@ whatever | |
main.py:1: error: Cannot find module named 'a' | ||
main.py:1: note: (Perhaps setting MYPYPATH or using the "--ignore-missing-imports" flag would help) | ||
main.py:1: error: Cannot find module named 'a.b' | ||
|
||
[case testPythonVersionTooOld10] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 1.0 | ||
[out] | ||
mypy.ini: [mypy]: python_version: Python major version '1' out of range (must be 2 or 3) | ||
|
||
[case testPythonVersionTooOld26] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 2.6 | ||
[out] | ||
mypy.ini: [mypy]: python_version: Python 2.6 is not supported (must be 2.7) | ||
|
||
[case testPythonVersionTooOld32] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 3.2 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like there's no test that checks that 3.3 is still accepted? We only have a test that checks that 3.2 is rejected. |
||
[out] | ||
mypy.ini: [mypy]: python_version: Python 3.2 is not supported (must be 3.3 or higher) | ||
|
||
[case testPythonVersionTooNew28] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 2.8 | ||
[out] | ||
mypy.ini: [mypy]: python_version: Python 2.8 is not supported (must be 2.7) | ||
|
||
[case testPythonVersionTooNew40] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 4.0 | ||
[out] | ||
mypy.ini: [mypy]: python_version: Python major version '4' out of range (must be 2 or 3) | ||
|
||
[case testPythonVersionAccepted27] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 2.7 | ||
[out] | ||
|
||
[case testPythonVersionAccepted33] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 3.3 | ||
[out] | ||
|
||
[case testPythonVersionAccepted36] | ||
# cmd: mypy -c pass | ||
[file mypy.ini] | ||
[[mypy] | ||
python_version = 3.6 | ||
[out] |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it easy to add test cases for this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could add testcases to test-data/unit/cmdline.test like this:
But a problem with that is that the output includes the full usage message, e.g.
which requires updating the tests frequently because the usage message changes each time we add a new flag.
Not sure I like tinkering with this more.