Re: [Pyobjc-dev] weakref-like behavior on ObjC subclasses

[James R E. <ea...@ba...>]

On Feb 26, 2008, at 10:58 , Ronald Oussoren wrote:

> That's right, the Python proxy to an Objective-C object retains the  
> Objective-C object, all references from Python share a single Python  
> proxy object (and use Python's refcounting to decide when that proxy  
> object should die).


That's what I figured and what I was afraid of.  Would that also mean  
that a Leopard-only approach of using an NSHashTable with  
NSPointerFunctionsZeroingWeakMemory would also fail, because the  
Python proxy to the object in the hash table would maintain a strong  
reference?

As for my particular use-case, I can achieve good-enough behaviour by  
letting windowWillClose: trigger the unregistering (deregistration?)  
of all the controller's listeners, but it's not ideal.

Thanks!
James

--
It's dead, Jim.