-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
Require Python 3.7.2 #1542
Require Python 3.7.2 #1542
Conversation
Pull Request Test Coverage Report for Build 2301412160
💛 - Coveralls |
I think we should block this until pylint 2.14 has been released. We might need to do a patch release for 2.13 still. |
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 spotted one if sys.version_info >= (3, 6, 2):
in astroid/nodes/scoped_nodes/scoped_nodes.py
.
There is also a match for 36
in the tox.ini
file which can be removed.
Grepping for minver="3.7
will also show a couple @test_utils.require_version(
decorators in tests that can be removed. Note that there also minver="3.7.2"
matches.
Rest LGTM 😄
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.
👍
The issue with python 3.11 come from main. I think it would be reasonable to temporarily skip this test for python 3.11, because the alternative seems to be making astroid understand the 3.11 code. |
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.
Looks good!
Regarding the 3.11 test failure: Tbh I'm not really sure what the issue is. I believe it appeared just recently (maybe with 3.11.0b1) but when testing that version locally, everything works fine. Maybe it's a linux and / or Github actions specific thing. (Only tested MacOS.)
Description
Require Python 3.7.2 to run
astroid
. Partner to pylint-dev/pylint#5921.One benefit of dropping 3.6 is to reduce risk from proposed performance-enhancing changes in #1536, where according to the complicated history of python/cpython#5481 and its (initial?) reversion on 3.6, it is possible that the behavior might vary there.
Type of Changes