Re: [Pyobjc-dev] ObjC GC with PyObjC?

[Ronald O. <ron...@ma...>]

On 3 Jun, 2009, at 23:54, Ronald Oussoren wrote:
>>
>
> I don't agree. There could be advantages for regular python as well,  
> IMHO removing CPython's refcounting is a necessary first step for  
> removing the GIL.  Removing the GIL would definitely be an advantage  
> for general python code, especially because using multiple  
> independent threads of execution is the only way to seriously  
> improve performance on modern hardware because sadly enough the  
> "wait a year and then my single-threaded code is twice as fast"-era  
> is over. Multiprocessing is a cool hack, but isn't a real solution;  
> I have a number of programs that use multiple threads and need  
> shared memory to get fast enough communications (basicly because  
> large objects get transferred between threads).

I have another reason for wanting this: better decoupling model code  
from the GUI.

I'm sure I'm not the only one that either has to jump through hoops to  
expose Python objects to the GUI (e.g. using the output of a library  
like SQLAlchemy in a GUI that uses Key-Value Bindings), or uses Cocoa  
datastructures such as NSArray in code that basicly has nothing to do  
with the GUI.

A version of Python that has more pervasive support for ObjC classes  
could make it easier to keep GUI code and non-GUI code.

Ronald