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 Sandeep, serhiy.storchaka, vinay.sajip, xtreak
Date 2020-02-02.08:28:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, my comment/request was prompted by whether this issue is a duplicate of bpo-26789, because it's not clear from the OP. If it is, then it can be closed as such. I don't think this is specifically a logging problem, more a case of how things become inaccessible as the interpreter shuts down. Any code which calls "open" (or some other builtins) would run into this problem, not just and not specifically logging. I'm not sure, but I don't believe we have a good answer to this problem in general.
Date User Action Args
2020-02-02 08:28:51vinay.sajipsetrecipients: + vinay.sajip, serhiy.storchaka, xtreak, Sandeep
2020-02-02 08:28:51vinay.sajipsetmessageid: <>
2020-02-02 08:28:51vinay.sajiplinkissue39513 messages
2020-02-02 08:28:51vinay.sajipcreate