[issue29183] Unintuitive error handling in wsgiref when a crash happens in write() or close()

[Chris Jerdonek]

Chris Jerdonek <chris.jerdonek at gmail.com> added the comment:

This may or may not be the same as what you're suggesting, Martin. But is another option to make close() a no-op if it is called a second time? Otherwise, it seems we'd need to make sure that no code path can result in close() being called twice (even during exception handling, etc).

----------
nosy: +chris.jerdonek

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue29183>
_______________________________________