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 JanVok, methane, r.david.murray, serhiy.storchaka, smurfix, vinay.sajip, vstinner, yselivanov
Date 2017-02-22.07:53:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487750025.59.0.500770559363.issue26789@psf.upfronthosting.co.za>
In-reply-to
Content
> sys.is_finalizing()

Good to know. Is the "sys" binding guaranteed to be around even when other builtins like "open" aren't available? In order to handle things "nicely" during shutdown, what guarantees can logging code rely on in terms of what's available? I'm assuming handling things nicely doesn't mean just swallowing any exceptions raised.
History
Date User Action Args
2017-02-22 07:53:45vinay.sajipsetrecipients: + vinay.sajip, vstinner, smurfix, r.david.murray, methane, serhiy.storchaka, yselivanov, JanVok
2017-02-22 07:53:45vinay.sajipsetmessageid: <1487750025.59.0.500770559363.issue26789@psf.upfronthosting.co.za>
2017-02-22 07:53:45vinay.sajiplinkissue26789 messages
2017-02-22 07:53:45vinay.sajipcreate