[Pythonmac-SIG] Building Mac extensions for Apple Python

[Kevin Ollivier]

Hi Jack,

Thanks for your help! I am also clueless as to why PyObject_Del would 
be causing that error message. Do those extensions get built with a 
framework build as well? I did some playing around (removing the 
extensions that were not building and changing $(scripts)/Lib/Mac to 
its new home), but I'm getting import errors for the mac modules during 
the import_BuildApplet phase. It cannot find import macfsn and 
EasyDialogs, which are of course in the CVS but the path is probably 
not set properly. Are these supposed to be copied over to 
/Applications/MacPython-OSX-2.3 before this portion of setup is run?

However, in the process of troubleshooting all of this I came across 
what I was really looking for - buildbundle.py. =) I thought I needed 
to install the Jaguar extensions to do this, but now I see that I don't 
have to. I've been getting ready to distribute the final release of a 
wxPython app I have been working on and I wanted to make it look more 
like a Mac application.

Now my wxPython application is running as a full-fledged .app bundle. 
=)  Runs great - the only thing I have yet to figure out is how to hook 
into the About and Preferences menus of the app, but that may be a 
wxPython issue.

Thanks,

Kevin

On Friday, January 3, 2003, at 03:37  PM, Jack Jansen wrote:

>
> On vrijdag, jan 3, 2003, at 15:59 Europe/Amsterdam, Kevin Ollivier 
> wrote:
>
>> Hi all,
>>
>> I've taken some time out to try out the new MacPython extensions to 
>> Apple's included Python, but I'm getting errors when trying to build.
>
> Kevin,
> I seriously broke this last week, when I modified a large part of the 
> source tree to move most of the Mac modules to Lib/plat-mac (from the 
> original Mac/Lib location). So, for the time being I've removed 
> Makefile.jaguar and setup.jaguar.py. As the schedule was extremely 
> tight (I started on this less than 48 hours before 2.3a1 came out) I 
> had no time to keep them functional.
>
> Although the breakage you see (_AE failing to build) is caused by an 
> earlier mod of mine it is difficult to fix right now.
>
> I will try to revive the MacPython-OSX-on-top-of-Python-2.2 
> (especially now I know that you are interested too, I could use a 
> hand!), but it will have to wait. First I have to get 
> MacPython-OS9-2.3a1 out the door, and that will be another few days.
>
> If you are willing to revive things, here's what needs to be done:
> - Check out the last versions of Makefile.jaguar and setup.jaguar.py 
> (checking out with a date of 28-dec-2002 should work)
> - Check out the previous version of Makefile, compare to the current 
> version and work out which bits I removed (mainly the copying of 
> $(srcdir)/Mac/Lib to the destination). That functionality will have to 
> go into Makefile.jaguar, but with $(srcdir)/Lib/plat-mac as the > source.
> - Then you'll have to find out where the bug you're seeing is coming 
> from. PyObject_Del is declared for python 2.2 (in 
> /usr/include/python2.2/objimpl.h) so I really have no idea why it 
> would fail...
> --
> - Jack Jansen        <Jack.Jansen@oratrix.com>        
> http://www.cwi.nl/~jack -
> - If I can't dance I don't want to be part of your revolution -- Emma 
> Goldman -
>
>