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

[Manoj Plakal]

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?

Yeah, I am porting Wing IDE (wingide.com)
to run on OS X and two of their extension
modules shared a source file, leading
to the import error. I have managed to get
it running without requiring 2-level namespace build
(changed the setup.py and import order a little bit).

Now I only wish there were a native
OS X version of Gtk (used by Wing). All I
see are a couple of inactive Sourceforge
projects (gtk-mac, gtk-quartz).

Manoj


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
>