[Python-Dev] reference leaks, __del__, and annotations
Michael Hudson
mwh at python.net
Tue Apr 4 14:19:36 CEST 2006
"Neal Norwitz" <nnorwitz at gmail.com> writes:
> On 4/3/06, Michael Hudson <mwh at python.net> wrote:
>> Greg Ewing <greg.ewing at canterbury.ac.nz> writes:
>>
>> > Michael Hudson wrote:
>> >
>> >> And if we want to have a version of __del__ that can't reference
>> >> 'self', we have it already: weakrefs with callbacks.
>> >
>> > Does that actually work at the moment? Last I heard,
>> > there was some issue with gc and weakref callbacks
>> > as well. Has that been resolved?
>>
>> Talk about FUD. Yes, it works, as far as I know.
>
> Not sure if everyone is talking about the same thing. This is still a
> problem (at least for me):
> http://svn.python.org/projects/python/trunk/Lib/test/crashers/weakref_in_del.py
>
> It creates a weakref to self in __del__.
Yes, but that has nothing to do with the cycle collector. I even have
a way to fix it, but I don't know if it breaks anything else...
Cheers,
mwh
--
I wouldn't trust the Anglo-Saxons for much anything else. Given
they way English is spelled, who could trust them on _anything_ that
had to do with writing things down, anyway?
-- Erik Naggum, comp.lang.lisp
More information about the Python-Dev
mailing list