[issue44612] inspect module points that could be using f-String

Eric V. Smith added the comment: Yes, thank you Leonardo! There are probably places in the stdlib where changing to f-strings would be a performance improvement. Of course finding those places is the challenge! -- nosy: +eric.smith ___ Python

[issue44612] inspect module points that could be using f-String

Leonardo Freua added the comment: Thanks, Ammar. I'll look. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44612] inspect module points that could be using f-String

Ammar Askar added the comment: Thanks for trying to help Leonardo! You might consider looking for easy issues on the bug tracker or reviewing open pull requests to help. Definitely take a look at the dev guide :) https://cpython-devguide.readthedocs.io/fixingissues/ -- resolution:

[issue44612] inspect module points that could be using f-String

Leonardo Freua added the comment: Understood. Anyway, it was good to try to help at this point. -- ___ Python tracker ___ ___

[issue44612] inspect module points that could be using f-String

Ammar Askar added the comment: As per https://bugs.python.org/issue36249 and https://bugs.python.org/issue38351 We don't generally do large-scale changes that are mostly formatting based. We would prefer that these sort of improvements happen when someone happens to be touching that code

[issue44612] inspect module points that could be using f-String

Change by Leonardo Freua : -- keywords: +patch pull_requests: +25648 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27100 ___ Python tracker ___

[issue44612] inspect module points that could be using f-String

New submission from Leonardo Freua : There are some points in inspect module (I counted 48 since version 3.7) that could be using f-String formatting instead of format(). Changing these points will improve code readability, it will also decrease the complexity at these points and not to