eyal.lotem+pyutils <at> gmail.com <eyal.lotem <at> gmail.com> writes:
> 
> That would be no worse than what happens now - but its still not
> perfect (__del__ ordering issues). Also, you would need to temporarily
> revive the cycles as mentioned above (to avoid accessibility of
> partially destructed objects).

The idea is to call all __del__'s *before* any object in the cycle is
deallocated (that is, call them manually rather than as part of deallocating
them). That way you shouldn't have the issues mentioned above.



_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to