-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Format status lines with f-strings #8846
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #8846 +/- ##
==========================================
+ Coverage 98.14% 98.24% +0.09%
==========================================
Files 107 107
Lines 34067 34108 +41
Branches 4030 4050 +20
==========================================
+ Hits 33435 33508 +73
+ Misses 456 424 -32
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Thanks for the 👀 |
Backport to 3.10: 💚 backport PR created✅ Backport PR branch: Backported as #8868 🤖 @patchback |
(cherry picked from commit 4dd8c80)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #8869 🤖 @patchback |
(cherry picked from commit 4dd8c80)
…#8868) **This is a backport of PR #8846 as merged into master (4dd8c80).** <!-- Thank you for your contribution! --> ## What do these changes do? Format status lines with f-strings ## Are there changes in behavior for the user? no, maybe a tiny performance improvement ## Is it a substantial burden for the maintainers to support this? no Co-authored-by: J. Nick Koston <nick@koston.org>
What do these changes do?
Format status lines with f-strings
Are there changes in behavior for the user?
no, maybe a tiny performance improvement
Is it a substantial burden for the maintainers to support this?
no