[Pythonmac-SIG] Python.h include errors on OS X, using Python 2.3 framework

[Jack Jansen]

On 24-feb-04, at 13:43, Paul Miller wrote:

>
>>> I'm trying to include Python.h into a Mach-O bundle build using CW 
>>> 8.3 on OS X 10.3.
>>
>> I think you're treading unknown ground, trying to use OSX Python from 
>> CodeWarrior. There's no reason why you shouldn't be able to get it to 
>> work, but as far as I know it hasn't been tried yet (i.e. if anyone 
>> else here tried it: please speak up!).
>
> Why does everything on the Mac have to be so DIFFICULT?

On Mac OS X things really aren't all that difficult: you just use make 
and gcc and be done with it, just like on any other unix machine... 
It's the legacy stuff from the pre-OSX era that can make things 
difficult.

> You know, I tried going the Mach-O bundle/framework route because I 
> couldn't get MacPython PythonCoreCarbon to load with GetDiskFragment.

I think you're going down a dead end, then: GetDiskFragment only works 
with CFM binaries. And the Python framework is a Mach-O framework. You 
could tie this into a CFM binary using a CFM to MachO bridge, but it is 
an incredible amount of work.

You want to host Python in a CFM-based application, right? Then 
PythonCoreCarbon and MacPython-OS9 is really your only feasible 
solution, so you should try to find out why PythonCoreCarbon doesn't 
want to load.
--
Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman