Why did logging not undergo PEP8 API change?

Ben Finney ben+python at benfinney.id.au
Mon Jul 30 19:33:01 EDT 2018

Skip Montanaro <skip.montanaro at gmail.com> writes:

> There was some discussion of the idea (before the thread predictably
> wandered off into the weeds). I've not found anything else obviously
> related to the topic. Perhaps it was nothing more than that the
> threading module had a PEP-8 champion while logging didn't?

Sometimes, even with a champion for improving the API through renames,
it doesn't happen. There is still the BDFL (or whatever comes to replace
that role) to reckon with

In that case, it was the inertia of the existing body of code using the
API names which gave justification to reject renames. I would expect
that was significant also in the decision not to change the ‘logging’
API names.

 \     “[F]reedom of speech does not entail freedom to have your ideas |
  `\    accepted by governments and incorporated into law and policy.” |
_o__)                                   —Russell Blackford, 2010-03-06 |
Ben Finney

More information about the Python-list mailing list