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 vinay.sajip
Recipients Jason.Baker, santoso.wijaya, vinay.sajip
Date 2010-05-01.09:51:58
SpamBayes Score 0.024146153
Marked as misclassified No
Message-id <123523.34784.qm@web25806.mail.ukl.yahoo.com>
In-reply-to <1272702173.49.0.935335399935.issue8581@psf.upfronthosting.co.za>
Content
----- Original Message ----

> From: Santoso Wijaya <report@bugs.python.org>
> 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?

I'm not objecting to the change on philosophical grounds, merely commenting that it doesn't happen in 2.7/3.2 and suggesting it's not worth fixing in 2.6/3.1.
History
Date User Action Args
2010-05-01 09:52:00vinay.sajipsetrecipients: + vinay.sajip, Jason.Baker, santoso.wijaya
2010-05-01 09:51:58vinay.sajiplinkissue8581 messages
2010-05-01 09:51:58vinay.sajipcreate