On 11 Jun 2014 12:31, "Antoine Pitrou" <antoine at python.org> wrote: > > Le 10/06/2014 21:30, Nikolaus Rath a écrit : > >> >> For me, having __del__ call close() does not qualify as a reasonable >> default implementation unless close() is required to be idempotent >> (which one could deduce from the documentation if one tries to, but it's >> far from clear). > > > close() should indeed be idempotent on all bundled IO class implementations (otherwise it's a bug), and so should it preferably on third-party IO class implementations. > > If you want to improve the documentation on this, you're welcome to provide a patch! We certainly assume idempotent close() behaviour in various places, so if that expectation isn't currently clear in the docs, suggestions for improved wording would definitely be appreciated! Cheers, Nick. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140611/4324709e/attachment.html>
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