I think (repeatedly) testing an app through IDLE is a reasonable use case. Would it be reasonable for shutdown to remove logging from sys.modules, so that a rerun has some chance of succeeding via its own import?
-jJ On 3/16/08, vinay.sajip <[EMAIL PROTECTED]> wrote: > Author: vinay.sajip > Date: Sun Mar 16 22:35:58 2008 > New Revision: 61431 > > Modified: > python/trunk/Doc/library/logging.rst > Log: > Clarified documentation on use of shutdown(). > > Modified: python/trunk/Doc/library/logging.rst > > ============================================================================== > --- python/trunk/Doc/library/logging.rst (original) > +++ python/trunk/Doc/library/logging.rst Sun Mar 16 22:35:58 2008 > @@ -732,7 +732,8 @@ > .. function:: shutdown() > > Informs the logging system to perform an orderly shutdown by flushing and > - closing all handlers. > + closing all handlers. This should be called at application exit and no > + further use of the logging system should be made after this call. > > > .. function:: setLoggerClass(klass) > _______________________________________________ > Python-checkins mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/python-checkins > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com