[Pyobjc-dev] was: [Swig] Swig for Mac OSX - Objective-C?

[Bob S. <bob...@ma...>]

:: Moved discussion to pyo...@li... because we strayed
significantly from Swig ::

on 1/29/02 12:50 PM, Steven Majewski wrote:
>
> pyobjc doesn't build with python 2.2 because of a bug in python 2.2 that's
> fixed in CVS
> 
> Include/abstract.h change this line:
> #define PyMapping_DelItemString(O,K)  PyObject_DelItemString((O),(K))
> 
> back to what it was in 2.1:
> #define PyMapping_DelItemString(O,K) PyDict_DelItemString((O),(K))
> 

I checked out the pyobjc from CVS, and ran "setup.py install" (probably with
the 2.2 version of Python, in case that makes a difference).

Then I started the 2.1 version of Python, added the 2.1 modules to the end
of the python_path, and got the following error:

>>> import pyobjc
dyld: /usr/local/bin/python2.1.exe Undefined symbols:
_PyObject_DelItemString
_PyType_IsSubtype

If I understand what you said above, I should not see this error under 2.1?

> There seem to be a few problems using AppKit GUI classes from a unix
> command line program running from Terminal.App -- there may also be
> a few Carbon problems, but I don't know if they are as bad. Is that
> what you're talking about doing, or are you going to roll your own
> command line front end?

We use the distributed object architecture (through an NSConnection). It
works quite well for GnuPlot.

Bob