[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Changes by Vinay Sajip : -- assignee: -> vinay.sajip resolution: -> wont fix stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Nick Coghlan added the comment: Dan and Amit worked out a patch for ConcurrentLogHandler (https://bugzilla.redhat.com/show_bug.cgi?id=858912) so I'm OK with rejecting this one. -- ___ Python tracker _

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Nick Coghlan added the comment: The particular app that is getting affected is clearing out and rebuilding the logging configuration without restarting in response to a notification that the application config has changed. This was working OK on 2.6, but started misbehaving when ported to 2.7.

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Vinay Sajip added the comment: I'm not against making this change, but I'm curious - why would a handler do clean-up I/O in its release() method (which is just for releasing the I/O lock) where it could just as easily override the close() method to do the same thing? It seems like programmer e

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

Changes by Nick Coghlan : -- nosy: +vinay.sajip type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue15960] logging.shutdown should cope with IO errors from handler.release methods

New submission from Nick Coghlan: logging.shutdown includes a try/except block to avoid emitting spurious IO errors while the interpreter is shutting down. This fails if a registered handler tries to do IO (such as calling flush()) in its release method. It would be better if the flush-and-clo