-
-
Notifications
You must be signed in to change notification settings - Fork 666
Deprecate python 3.9 support #5052
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
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #5052 +/- ##
===========================================
- Coverage 98.58% 98.58% -0.01%
===========================================
Files 304 304
Lines 23725 23723 -2
===========================================
- Hits 23389 23387 -2
Misses 336 336 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 @Saransh-cpp, I fixed the ones you pointed out and found a couple others |
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.
Fixing a mistake from the pre-commit changes that was not caught by tests
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.
Nice, thanks @kratman!
It would be nice to set strict=True
in all zip
s (in another PR by someone else) to avoid silent bugs.
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! I'm okay with dropping support for Python 3.9 (I'm coming from @Saransh-cpp's comment at #4490), but I would delegate the decision to others.
Yeah I agree. I did not want to do both in this single PR. It also bothers me that the tests did not catch the error from the edit: I see there is already a ticket for it. I will just add more context |
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 to me, thanks!
Description
This is earlier than necessary (~October), but it makes the switch to numpy 2.0 easier.
Related: #4183
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #)
Important checks:
Please confirm the following before marking the PR as ready for review:
nox -s pre-commit
nox -s tests
nox -s doctests