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 mdt
Recipients mdt, vinay.sajip
Date 2013-08-07.11:23:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375874584.95.0.381166066073.issue18671@psf.upfronthosting.co.za>
In-reply-to
Content
for a logging library the important thing would be to not loose the information that was meant to log. as i said i do alot of long-running huge-data-processing scripts in py using the library. if the logging breaks but doesnt log what was intended to log i judge this a major problem. and furthermore: it is so simple to add both information: the data that was to be logged plus the state that an error occured while formatting and where the log-call was made.
History
Date User Action Args
2013-08-07 11:23:04mdtsetrecipients: + mdt, vinay.sajip
2013-08-07 11:23:04mdtsetmessageid: <1375874584.95.0.381166066073.issue18671@psf.upfronthosting.co.za>
2013-08-07 11:23:04mdtlinkissue18671 messages
2013-08-07 11:23:04mdtcreate