This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tinchester
Recipients ariebovenberg, docs@python, eric.smith, rhettinger, tinchester, vinay.sajip
Date 2022-02-04.11:24:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I mean, I agree with your point about being able to accidentally format twice when using the standard library logger.

I'm not a core dev but I think getting new APIs in will be challenging. And if by some fluke of chance you did get the approval to introduce new logging APIs, there are better APIs out there (look at the structlog library). Also the old APIs would have to stay for a *long* time since everybody's using them.

Adding clever typing overloads seems actually realistic and useful to me. But that depends on the LiteralString PEP being accepted and people actually running MyPy. That's probably the best we can do, apart from some documentation.
Date User Action Args
2022-02-04 11:24:50tinchestersetrecipients: + tinchester, rhettinger, vinay.sajip, eric.smith, docs@python, ariebovenberg
2022-02-04 11:24:50tinchestersetmessageid: <>
2022-02-04 11:24:50tinchesterlinkissue46200 messages
2022-02-04 11:24:50tinchestercreate