Guido van Rossum <guido <at> python.org> writes: > > If you want to ensure buffers are flushed, why not call self.flush() > for writable files outside the try/except? If flush() fails it *is* a > real problem. Well, my concern is less about flushing writable files (they will be implemented in C and the flushing will probably be ok) than Python-written file-like types, like SocketIO or any third-party class. Anyway, let's keep silencing exceptions and we'll see if anyone complains about it. Regards Antoine.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4