[Pyobjc-dev] pyobjc on 2.2.1 & non-framework builds

[Bill B. <bb...@co...>]

I committed changes that allow pyobjc to build with non-framework 
installs and to build against Python 2.2.1 (the latest version 
available via Fink).

It works fine;  the most intrusive change was the presence of PyBool -- 
a new type as of 2.3.   I changed PyBool_Check to a non-operation and 
changed PyBool_FromLong() to be PyInt_FromLong().   This should be 
relatively equivalent at runtime.

The ObjC interface seems to work fine, but the Cocoa based stuff is 
broken -- I'm not sure if this is related to 2.2, to non-Framework 
builds, or just the state of the current development.

In any case -- Ronald, I must extend a HUGE note of gratitude for all 
of your work on this.  It is excellent!!!

Also -- I believe that we can make standalone scripts work fine even if 
they launch UI sessions.  I built a little app called PythonLauncher 
that can be used to springboard the launching of a script that uses the 
UI.  It provides a full blown "bundle" environment, as required by the 
X environment, but allows multiple copies to be launched.  I'll have to 
hack on it....

Comment:   Foundation should not really be a part of Cocoa.  I.e. I 
should be able to do "from Foundation import NSString" -- not "from 
Cocoa.Foundation import NSString".   There are platforms upon which 
Foundation exists, but Cocoa might not -- this is especially true as 
support for GnuStep is reintroduced (or, likely, rewritten).

b.bum