Closed effigies closed 1 year ago
Patch coverage: 80.00
% and project coverage change: -0.64
:warning:
Comparison is base (
64bfa89
) 81.77% compared to head (c1a8983
) 81.13%.:exclamation: Current head c1a8983 differs from pull request most recent head 4da0a35. Consider uploading reports for the commit 4da0a35 to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
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 INTERNALERROR
...
It happened on 99df677708b1a25608b705daadb120202558971d 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