Michael Hudson wrote:
> While you can probably do this (after all, most of the time
> __new__/__init__ and __enter__ will be called in rapid succession) I
> really think the RAII meme doesn't apply to Python; you generally want
> a resource to be acquired for a period of definite extent, and objects
> in Python have indefinite extent, unlike C++ where automatic variables
> have definite extent (Common Lisp terminology here).
Using the RAII term was probably a bad idea, as it brings in too many
extra connotations (like the converse 'RRID' - 'resource release is
destruction').
Anyway, Guido's taking the option of not providing any explicit
guarantees at this point, which is probably the most sensible idea.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.blogspot.com
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