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
If #12630 lands, I/O errors from flush() will be ignored when a BufferedWriter is dropped. Is this the right decision, so this trigger a task failure? Should it be dynamically controllable?
This sort of decision will set precedent for future methods such as a manual close(self) method (should close errors be ignored by default?)