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 taleinat
Recipients cheryl.sabella, ned.deily, rhettinger, serhiy.storchaka, taleinat, terry.reedy
Date 2019-09-14.12:46:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I've also seen these occasionally, but I haven't yet found a way to reproduce consistently.

Regardless, IMO the shutdown close() and _close() should be the places handling shutdown-related exceptions if possible.  In all of the tracebacks posted here, as well as those in #35263 and #17822, one such method is in the call chain, and it could simply catch and handle the raised exception.

I also think these are clear improvements that are safe to include, even without understanding the full details of the sequences of events leading to the errors.
Date User Action Args
2019-09-14 12:46:46taleinatsetrecipients: + taleinat, rhettinger, terry.reedy, ned.deily, serhiy.storchaka, cheryl.sabella
2019-09-14 12:46:46taleinatsetmessageid: <>
2019-09-14 12:46:46taleinatlinkissue35379 messages
2019-09-14 12:46:46taleinatcreate