[Pythonmac-SIG] Extensions for static versus framework MachoPython

[Jack Jansen]

On woensdag, juli 10, 2002, at 02:38 , bill fancher wrote:
> Having opened this can of worms, I almost feel obliged to take 
> a look, assuming it's still an issue. If no one else expresses 
> interest, feel free to mail diffs if that's easier than putting 
> them on sourceforge.

I've put them on sourceforge (this'll also make sure I either 
fix them or delete them in a finite amount of time:-). They're 
at http://www.python.org/sf/579841 .

> FWIW, when I do something similar here I get:
>
> Fatal Python error: Interpreter not initialized (version mismatch?)
> Abort

That is indeed what I expected.

> This seems to me to be the correct behavior. (It's what you had 
> originally expected to happen, IIRC.) To try it out, I cooked 
> up two_level_namespace sha and _AE modules. Of course the 
> libpython2.3.dylib that my test modules are linked against is 
> not the same as what you're using there...

Did you test with a "normal" dylib build, or with a 
dylib-linked-from-a-framework build?

BTW: the bit of your patch that we agree on is the bit about 
getting --enable-shared to work. Is it possible to extract that 
from the rest, so we can then happily continue debating 
linked-framework-built-externally vs. 
self-contained-framework-built-from-makefile? (The other bit I 
agreed with, that the Carbon modules shouldn't be built for a 
non-framework build, was a silly mistake on my part and has been 
fixed already).
--
- 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 -