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 asvetlov, jryan, serhiy.storchaka, steven.daprano, vinay.sajip, vstinner, xtreak, yselivanov
Date 2020-10-31.06:39:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Should this be closed and pushed back to fixing logging?

It's not particularly a logging issue, though it can surface in logging because that's a mechanism to notify users about stuff. After all, most parts of the stdlib would expect open() to always be available. ISTM it's more a case of shutdown behaviour and user expectations relating to that. Users should be able to avoid any logging by calling logging.shutdown(), which can be done during a controlled process shutdown in user code.
Date User Action Args
2020-10-31 06:39:05vinay.sajipsetrecipients: + vinay.sajip, vstinner, steven.daprano, asvetlov, serhiy.storchaka, yselivanov, xtreak, jryan
2020-10-31 06:39:05vinay.sajipsetmessageid: <>
2020-10-31 06:39:05vinay.sajiplinkissue42203 messages
2020-10-31 06:39:05vinay.sajipcreate