You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #53, #64 et al. allowing instantiation of StdioManager objects with a useful lifetime before and after use as a context manager, as well as independent of a managed context, the question arises as to what the behavior should be when a given stream in the internal tuple is .close()d more than once.
At this point, I believe a repeated .close() on a stream will raise ValueError? In some situations this is probably desired; but in others it might not be.
Or, for consistency, the behavior should perhaps always be the same.
This is loosely related to #42, in that the exception behavior is more a part of the API than not.
The text was updated successfully, but these errors were encountered:
With #53, #64 et al. allowing instantiation of
StdioManager
objects with a useful lifetime before and after use as a context manager, as well as independent of a managed context, the question arises as to what the behavior should be when a given stream in the internaltuple
is.close()
d more than once.At this point, I believe a repeated
.close()
on a stream will raiseValueError
? In some situations this is probably desired; but in others it might not be.Or, for consistency, the behavior should perhaps always be the same.
This is loosely related to #42, in that the exception behavior is more a part of the API than not.
The text was updated successfully, but these errors were encountered: