[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Vinay Sajip added the comment: Closing, as no specific proposals received. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Vinay Sajip added the comment: > Should I make use of a single logger object in my library, multiple loggers > in a tree, or multiple unrelated loggers? Since I have just one public module, > I'm tempted to say that I should just use one logger object. Yes. The advanced logging tutorial (part

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Raymond Hettinger added the comment: > Then we could establish the "gold standard" for logging and write > about it in the HOWTO. There really isn't a gold standard. There are many widely varied logging practices, each adapted to the needs of the application. The module is complicated

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

pms.coder added the comment: I would be happy to see such HOWTO, so we could relay on actual documentation instead of the "Internet". I think the best approach would be to get those 10-20 questions you ( Nathaniel Manista) just asked and post them to python-dev mailing list, so senior

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Nathaniel Manista added the comment: Something... related, that may perhaps belong in a separate issue, but that I want to at least mention here because it would be solved if logging-in-libraries best practices were authoritatively documented and exemplified: it's just too consarn easy to

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Change by Tim Lesher : -- nosy: +tlesher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

Raymond Hettinger added the comment: FWIW, I think the practices vary somewhat widely and that none of your questions have generally agreed upon answers. Part of the reason that there are so many ways to go is that the package was modeled after Java APIs where the practices and needs were

[issue34590] "Logging HOWTO" should share an example of best practices for using logging in a library

New submission from Nathaniel Manista : https://docs.python.org/3.8/howto/logging.html#configuring-logging-for-a-library is a bit too short and doesn't answer some questions that I have as a library author about the best ways to use logging in a library. Should I make use of a single logger