[issue36249] f-string should be the default placeholder

Change by Serhiy Storchaka : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue36249] f-string should be the default placeholder

Karthikeyan Singaravelan added the comment: New code might use f-strings as needed but refactoring old code just for f-strings could result in large change that pollutes git history. Generally large refactorings like this are rejected like making all code PEP 8 compatible is another example.

[issue36249] f-string should be the default placeholder

Change by Akash Shende : -- keywords: +patch pull_requests: +12237 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-li

[issue36249] f-string should be the default placeholder

New submission from Akash Shende : Currently lot of code still uses old placeholder and .format() methods for formatting the string. Lets convert them all to f-string "%s" % (name) => f'{name}' "{name}".format(name="yoyo") = > f'{name}' -- components: Library (Lib) messages: 337560 no