➜

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 rhettinger
Recipients dasilver@cisco.com, r.david.murray, rhettinger, vinay.sajip
Date 2015-10-09.00:44:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444351491.65.0.201625711847.issue25344@psf.upfronthosting.co.za>
In-reply-to
Content 
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 series of normal logging calls, followed by either a transaction-commit or transaction-rollback.
History
Date User Action Args
2015-10-09 00:44:51rhettingersetrecipients: + rhettinger, vinay.sajip, r.david.murray, dasilver@cisco.com
2015-10-09 00:44:51rhettingersetmessageid: <1444351491.65.0.201625711847.issue25344@psf.upfronthosting.co.za>
2015-10-09 00:44:51rhettingerlinkissue25344 messages
2015-10-09 00:44:51rhettingercreate