[Pythonmac-SIG] Why dynload_next.c rather than dynload_shlib.c?

[Zachary Pincus]

As of Python 2.5a2, python.org python should use dynload_shlib.c on  
10.3 and 10.4. I didn't realize that Apple's python was built  
differently...

Anyhow, if you want to build your own Py2.4 with dynload_shlib the  
patch is pretty easy. You can search for the patch on sourceforge  
(it's against 2.5 but it applies cleanly to 2.4 too, I think) or I  
can send it to you.

This peculiarity dates from earlier versions of OS X that did not  
have dlopen() functionality -- then the next APIs were all that there  
were.

Zach



On Apr 26, 2006, at 11:58 PM, Phil Thompson wrote:

> Apple's Python seems to be built with dynload_shlib.c which allows  
> it to
> handle extension modules built as bundles and dynamic libraries.
>
> python.org Python uses dynload_next.c which means that extension  
> modules must
> be built as bundles.
>
> Is there any particular reason for this (I'm new to MacOS)?
>
> Thanks,
> Phil
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig