-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Drop support for running with 3.4 #6592
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
Conversation
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.
Thanks! It's great to be able to drop 3.4 workarounds. I found a few remaining 3.4 references that should probably be updated in tox.ini
.
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.
LGTM, but see Jukka's comment about tox.
I also found references to 3.3 (!) in fastparse.py and fastparse2.py.
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.
Have you tried to run it with 3.4? Does it even make it to that error message? For all entry points?
Yes I checked this in a docker container with 3.4.10, it does indeed cause the error to be shown. I tested |
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.
Ship it!
Fixes #6564
This PR was a bit larger than I expected, but after the test failure in #6591 I am keen to move forward with dropping support for 3.4.