➜

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 santoso.wijaya
Recipients Jason.Baker, santoso.wijaya, vinay.sajip
Date 2010-05-01.08:22:51
SpamBayes Score 0.03409792
Marked as misclassified No
Message-id <1272702173.49.0.935335399935.issue8581@psf.upfronthosting.co.za>
In-reply-to
Content 
File-like objects handle multiple close() gracefully, silently making the second and subsequent close() calls to an already closed I/O object do nothing. Why can't the same expectation be applied to logging handlers?
History
Date User Action Args
2010-05-01 08:22:53santoso.wijayasetrecipients: + santoso.wijaya, vinay.sajip, Jason.Baker
2010-05-01 08:22:53santoso.wijayasetmessageid: <1272702173.49.0.935335399935.issue8581@psf.upfronthosting.co.za>
2010-05-01 08:22:52santoso.wijayalinkissue8581 messages
2010-05-01 08:22:51santoso.wijayacreate