[issue29988] with statements are not ensuring that __exit__ is called if __enter__ succeeds
Raymond Hettinger
report at bugs.python.org
Wed Aug 21 18:28:13 EDT 2019
Raymond Hettinger <raymond.hettinger at gmail.com> added the comment:
Historically, in C, Python, and and low-level interrupt programming it was the responsibility of a person writing a signal handler to make minimal variable edits and not disrupt anything else in the ecosystem.
Are we changing that rule? (I'm still at the cringing stage and possibly haven't evolved my views yet).
----------
nosy: +rhettinger
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29988>
_______________________________________
More information about the Python-bugs-list
mailing list