[issue1295] logging records cache the result of formatException()

Vinay Sajip added the comment: I've updated the docs (Formatter.format) to mention the caching and its effect on multiple formatters. -- nosy: +vsajip __ Tracker <[EMAIL PROTECTED]> __ ___

[issue1295] logging records cache the result of formatException()

Thomas Heller added the comment: I think that a warning or an example in the docs would be nice, but I have no time to make a patch for that. -- resolution: -> wont fix status: open -> closed __ Tracker <[EMAIL PROTECTED]>

[issue1295] logging records cache the result of formatException()

Guido van Rossum added the comment: I think so. On 10/18/07, Thomas Heller <[EMAIL PROTECTED]> wrote: > > Thomas Heller added the comment: > > > > This is tough. On the one hand you are right that different classes that > > > have different formatException() methods aren't treated correctly; on

[issue1295] logging records cache the result of formatException()

Thomas Heller added the comment: > > This is tough. On the one hand you are right that different classes that > > have different formatException() methods aren't treated correctly; on > > the other hand I think the caching is important for other cases where > > there are multiple loggers all usin

[issue1295] logging records cache the result of formatException()

Guido van Rossum added the comment: This is tough. On the one hand you are right that different classes that have different formatException() methods aren't treated correctly; on the other hand I think the caching is important for other cases where there are multiple loggers all using the default

[issue1295] logging records cache the result of formatException()

New submission from Thomas Heller: I needed two logging handlers in my application, one notifiying the user of errors, the other writing errors to a logfile. So I created a custom subclass of logging.Formatter and redefined the formatException() method that returned a summary of the exception li