Vinay Sajip <vinay_sa...@yahoo.co.uk> added the comment:
> 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue42203> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
