Do other Python GUI toolkits require this?

James Stroud jstroud at
Wed Apr 18 23:45:19 CEST 2007

Kevin Walzer wrote:
>  From the introduction to PyObjC, the Python-Objective-C bridge on Mac 
> OS X:
> "As described in Objective-C for PyObjC users the creation of 
> Objective-C objects is a two-stage process. To initialize objects, first 
> call a class method to allocate the memory (typically alloc), and then 
> call an initializer (typically starts with init). Some classes have 
> class methods which perform this behind the scenes, especially classes 
> that create cached, immutable, or singleton instances."
> An example:
> myObject = NSObject.alloc().init()
> I know Tkinter doesn't require any manual memory allocation of this 
> sort. Does wxPython, PyQt, PyGtk require anything like this when 
> creating objects?

This appears more or less unique to Objective C. It looks that with 
PyObjC, you have to interact with the Objective C runtime to manage 
memory. This is not required, thankfully, with any other GUI tookits 
I've seen.

I think the main difference is that PyObjC is not a GUI toolkit per se, 
but is simply a means to make the Objective C runtime (and hence Cocoa) 
available via a python layer.


More information about the Python-list mailing list