Message380044
> 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:05 | vinay.sajip | set | recipients:
+ vinay.sajip, vstinner, steven.daprano, asvetlov, serhiy.storchaka, yselivanov, xtreak, jryan |
2020-10-31 06:39:05 | vinay.sajip | set | messageid: <1604126345.58.0.627850388279.issue42203@roundup.psfhosted.org> |
2020-10-31 06:39:05 | vinay.sajip | link | issue42203 messages |
2020-10-31 06:39:05 | vinay.sajip | create | |
|