-
Notifications
You must be signed in to change notification settings - Fork 59
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
STY: Miscellaneous cleanups #645
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #645 +/- ##
==========================================
- Coverage 81.77% 81.13% -0.64%
==========================================
Files 20 20
Lines 4394 4400 +6
Branches 1264 0 -1264
==========================================
- Hits 3593 3570 -23
- Misses 797 830 +33
+ Partials 4 0 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
a6f41ba
to
9d442d4
Compare
DOC: Fix deprecated intersphinx mapping
lgtm! thank you! |
Are these random 3.11 failures expected? |
no, i didn't notice it... and it's not even test failure, but some |
It happened on 99df677 as well, so at least I'm not introducing it with something I've done here. My guess is it's an out-of-memory error causing an xdist worker to get killed. |
Types of changes
Summary
While looking into type checking failures, some style issues caught my eye. Rather than bundle them in, I am putting them in a standalone PR. This PR has three commits, each of which can be considered separately, if you disagree.
__file__
calls withimportlib.resources
where appropriate. I wrapped it in a pytest fixture to save repetition. This is considered good hygiene, as__file__
may not be available when packages are zipped.f"...{str(x)}..."
idiom. This is a straightforward win for readability.pyupgrade --py38-plus
, followed byblack
for cleanup. This auto-upgrades from idioms that are no longer needed to ones that are universally supported in 3.8+.Closes #282.
Checklist