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 ag6502
Recipients ag6502, vinay.sajip
Date 2008-03-03.11:44:00
SpamBayes Score 0.010327964
Marked as misclassified No
Message-id <1204544641.93.0.838688288715.issue2216@psf.upfronthosting.co.za>
In-reply-to
Content
I thougt it was a bug because when calling close() handlers are removed
from some data structure (the global dictionary and the global list) but
they're left inside the loggers they're attached to. Now I understand
that this is a responsibility of who attached the handler; probably my
patch would break or just behave differently with code that already
managed to remove logging handlers from loggers explicitly or that
relied on the fact that even a "closed" handler can still be notified.

Having the logging module to work correctly in IDLE and other
environments that keep a running instance of the interpreter provided
that shutdown is called would have been just a lucky nice side effect of
"fixing" handler.close (of course those IDEs will still have potential
problems with any module that keeps an internal state).
History
Date User Action Args
2008-03-03 11:44:02ag6502setspambayes_score: 0.010328 -> 0.010327964
recipients: + ag6502, vinay.sajip
2008-03-03 11:44:01ag6502setspambayes_score: 0.010328 -> 0.010328
messageid: <1204544641.93.0.838688288715.issue2216@psf.upfronthosting.co.za>
2008-03-03 11:44:01ag6502linkissue2216 messages
2008-03-03 11:44:00ag6502create