gh-110558: Enable ruff's pyupgrade rules when running on Argument Clinic#110603
gh-110558: Enable ruff's pyupgrade rules when running on Argument Clinic#110603AlexWaygood merged 1 commit intopython:mainfrom
Conversation
|
Thanks, both! I chatted with @hugovk at the sprint (you're missed @erlend-aasland 😢), and I think there probably aren't any other rules that are worth enabling right now (but feel free to propose any more that that you think would be useful!) |
For these DevOps things, I fully trust you two! :) It is very nice that we're getting more automated machinery in place in the CPython repo; I love it! I wish I was in Brno with y'all; it is a very nice city IMO. |
|
Thanks @AlexWaygood for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12. |
|
GH-110609 is a backport of this pull request to the 3.12 branch. |
…nt Clinic (pythonGH-110603) (cherry picked from commit fc811c8) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
These are more opinionated, lint-style checks than the existing
pyflakesrules that we currently have enabled on Argument Clinic, following #110559. The full list of pyupgrade rules is at https://docs.astral.sh/ruff/rules/#pyupgrade-up.Thoughts? Is this a useful addition?