> which leads me to believe that __del__ would not be called in the current > implementation. If people are going to be subclassing more than the > traditional builtin types I think __del__ methods will have to be supported. Correct, __del__ is not yet supported. (__coerce__ is, as of 2.2a4 at least). I'm not sure that __del__ should be supported though: it causes problems with the garbage collector. The GC won't destroy objects with a __del__ method because it's impossible to decide in which order to finalize mutually referencing objects. Can somebody (e.g. whoever started this thread) present a good reason why __del__ should be supported? --Guido van Rossum (home page: http://www.python.org/~guido/)
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