Re: [Pyobjc-dev] PyObjC & Fink

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

On Monday, September 23, 2002, at 08:02 AM, Ronald Oussoren wrote:
> I just noticed that I sent my reply just to Bill:
>
> On Monday, Sep 23, 2002, at 08:40 Europe/Amsterdam, Ronald Oussoren 
> wrote:
>
>> I wouldn't mind pushing out a new snapshot. IMHO it should be marked 
>> experimental, mostly because of a memory leak whose source I've as of 
>> yet have been unable to locate.
>>
>> BTW. Does Fink install a Python framework? PyObjC probably won't be 
>> very usefull unless Python is installed as a framework. But then 
>> again, maybe a normal Unix install works just as well, as long as GUI 
>> scripts are packaged inside '.app' directories.

Fink installs the "normal" python build.  However, pyobjc is 
*extremely* useful without the framework.  Namely, it can be used to do 
very powerful command line scripting -- automating various tasks on the 
system.  There are a number of powerful ObjC APIs that have nothing to 
do with the GUI -- Address Book and NetInfo, for example.

In any case, even for building apps, the non-framework build is still 
very useful.  In particular, embedding the interpreter works quite 
nicely for adding scripting to "traditional" Cocoa apps.

I'll have a look at the memory looks as time permits...

BTW: The fix you [Ronald] mentioned for compiling pyobjc w/Python 2.2 
worked except that it seems the precompiler has gone into an infinite 
loop while compiling-- it has been using 70% of the CPU for over 10 
minutes!

gcc -DNDEBUG -O3 -Wall -Wstrict-prototypes -I/sw/include/python2.2 -c 
Modules/objc/register.m -o 
build/temp.darwin-6.1-PowerMacintosh-2.2/register.o -g -O0 
-DOBJC_PARANOIA_MODE -DPyOBJC_UNIQUE_PROXY -DMACOSX

Maybe I'll let it run -- that is one BIG file...   maybe I need to 
regenerate it for 2.2 vs. 2.3??

b.bum