-
Notifications
You must be signed in to change notification settings - Fork 296
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: Apply pyupgrade suggestions #3147
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #3147 +/- ##
=======================================
Coverage 50.00% 50.00%
=======================================
Files 53 53
Lines 3914 3916 +2
=======================================
+ Hits 1957 1958 +1
- Misses 1957 1958 +1 ☔ View full report in Codecov by Sentry. |
I want to hold off on this until the full release, then we'll probably just do what we're doing over in smriprep. We can take care of pyupgrade, flake8, and all that in a single PR. |
pyupgrade --py310-plus Also manually change a few `.format()` calls to f-strings.
673d9b0
to
e09e36a
Compare
Follow-up to nipreps/smriprep#397. This should replace #3185 and #3147. I would review this commit-by-commit, and skip c0f2183, which was a pretty safe run of `ruff format` and `ruff --fix`. It's dominated by quote changes, so I would ignore it. Everything else could stand a review.
I think this should be covered by ruff now. |
Not entirely. For example, switching to f-strings is not covered by ruff (pyupgrade rules). |
Ah, do you want to go ahead and re-upgrade? Note that |
Let me have a look first:
|
Changes proposed in this pull request
pyupgrade --py310-plus
Also manually change a few
.format()
calls to f-strings.