refactor: prefer f-strings to .format in docs #13317
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Because Mypy currently requires 3.6+, this merge request begins the process of refactoring the use of various format styles such as
.format
, with the use of f-strings. This intentionally leaves behind certain formatting examples which are being used to demonstrate errors, such as:Python added f-strings in version 3.6, with PEP 498. F-strings are a flexible and powerful way to concatenate strings. They make the code shorter and more readable, since the code now looks more like the output. Finally, there is also a performance benefit to using f-strings, which is an additional reason to advocate for their usage in examples.
Finally, this also leverages PEP515, underscores in numeric literals, in two locations, to improve legibility while reading numbers larger than 999 that are not years.
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)