<br><div><span class="gmail_quote">On 4/1/06, <b class="gmail_sendername">Jim Jewett</b> <<a href="mailto:jimjjewett@gmail.com">jimjjewett@gmail.com</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Nick Coghlan<br>> A simple Boolean attribute (e.g. __finalized__) should be enough. ...<br>> If it's both present and true, the GC can ignore the finaliser on that instance<br><br>That doesn't really take care of resource release, which needs to be
<br>called, and called early.(And the name will sound odd if it holds<br>resources only sometimes, so that it has to flip the __finalized__<br>attribute.)</blockquote><div><br>Well, I don't want to sound too gross, but any such class could store its resources *in* __finalized__, leaving it an empty container when there is no resource to release.
<br></div><br></div>D'oh--not-sounding-gross-failed-ly y'rs,<br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br><br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!