-
Notifications
You must be signed in to change notification settings - Fork 2.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
chore: drop Python 3.5 #3719
chore: drop Python 3.5 #3719
Conversation
5cd529b
to
4fe5711
Compare
I can fix the deprecation warning I think, and PyPy 3.8 NumPy might be buggy still. I’ll drop PyPy 3.6, it is unsupported. |
I think this was fixed… |
Forgot we have a pytest.ini for some situations. Will have to check. |
I'd rather disallow non-f-strings via pylint, vs. have flynt always running to try to convert them. It's actually only a hair stronger at converting them than pyupgrade unless you pass |
0f71f9f
to
20046be
Compare
I left off the Flynt addition, but kept the smart quotes one + fix. |
d7af4b6
to
bc9bf7f
Compare
Any thoughts to the failing valgrind run? Will not be able to work on this more for now. |
bc9bf7f
to
bca56c0
Compare
We have 3 new errors in valgrind when going from numpy 1.21 to numpy 1.22, so I left this at numpy 1.21 for Python < 3.10. Ready for review. |
Dropping Python 3.5 support.
Description
Suggested changelog entry: