[issue42203] Unexpected behaviour NameError: name 'open' is not defined

[Vinay Sajip]

Vinay Sajip <vinay_sajip at 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 <report at bugs.python.org>
<https://bugs.python.org/issue42203>
_______________________________________