[Fwd: Re: [Pythonmac-SIG] OS X import bug?]

[Manoj Plakal]

Actually, instead of only one or
the other, it might be a better
idea for Python to provide
a distutils option for
flat or 2-level namespace when
building extension modules. I added
this as a follow-up to my bug report
on Sourceforge:
   http://sourceforge.net/tracker/index.php?func=detail&aid=508779&group_id=5470&atid=105470

Manoj


Manoj Plakal wrote:

> 
> Marcel,
> 
> Which modules are these? From the replies I saw
> on c.l.py, it seems that the two-level
> setup corresponds to the way extension
> modules are built and used on Linux
> and Windows (symbols within modules
> don't clash with each other).
> http://groups.google.com/groups?hl=en&threadm=j4sn8uu517.fsf%40informatik.hu-berlin.de&prev=/groups%3Fnum%3D25%26hl%3Den%26group%3Dcomp.lang.python%26start%3D75%26group%3Dcomp.lang.python
> Why do some modules need the flat namespace?
> 
> 
> Marcel Prastawa wrote:
> 
>> This is not really a bug. Some (very useful) modules will not compile 
>> as two-level namespace binaries, at least not without some 
>> considerable effort.
>>
>> It looks like you're porting an app... Be aware that there is an issue 
>> with dynload_next (see Bob Ippolito's messages). I've gotten into some 
>> trouble with identically named binaries (lots of renaming), I've 
>> switched to libdl now (thanks Bob!).
>>
>> Marcel
>>
> 
> 
>