[issue25344] Enhancement to Logging - Logging Stack

Changes by Adam : -- nosy: -azsorkin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/m

[issue25344] Enhancement to Logging - Logging Stack

Roundup Robot added the comment: New changeset 3ad8a2d34d01 by Vinay Sajip in branch '2.7': Closes #25344: Added cookbook recipe to show buffering of logging events. https://hg.python.org/cpython/rev/3ad8a2d34d01 New changeset 7cc3a8141022 by Vinay Sajip in branch '3.4': Closes #25344: Added coo

[issue25344] Enhancement to Logging - Logging Stack

Vinay Sajip added the comment: This is already supported. There is a logging.handlers.MemoryHandler which allows you to buffer logging events and then pass the buffered events to another handler when some condition is met, such as e.g. buffer full or some severity threshold is exceeded. Flushi

[issue25344] Enhancement to Logging - Logging Stack

Changes by Adam : -- nosy: +azsorkin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue25344] Enhancement to Logging - Logging Stack

Raymond Hettinger added the comment: This seems like a reasonable use case and is worth considering. Offhand, I don't see how a user could easily implement this on their own without hacking the logging module internals. What would be needed is some support for begin-logging-transaction, a ser

[issue25344] Enhancement to Logging - Logging Stack

R. David Murray added the comment: I'm guessing you could write a custom hander that would do that. It might be something more suited for a recipe or pypi package. -- nosy: +r.david.murray, vinay.sajip ___ Python tracker

[issue25344] Enhancement to Logging - Logging Stack

New submission from David Silverman: It would be useful to have the ability to push logs onto a stack. This way you can log events to the stack. If an error occurred, you could pop the stack and output the log events. If no error occurred, you could pop the stack and discard the logs. An exam