This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients ned.deily, ronaldoussoren
Date 2012-10-26.09:17:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Apple seems to have switched to using dlopen in their version of getpath.c (see <>, this is the version in OSX 10.8.2)

This causes a problem for some people, as noticed on the pythonmac mailing list. This is something we should test before applying my patch to avoid regressions.

Message-Id: <> says:

I am trying to work with Apple Mountain Lion's install of Python 2.7. I
have a language interoperability tool, Babel, that used embedded Python when
other languages are calling Python (c.g., C++ calling Python). My
fundamental problem is that sys.path is not being initialized the same
when I dlopen(libpython2.7.dylib) and initialize Python compared with
how the sys.path is set when the Python executable is called directly.
This causes Python to fail to load the numpy module used by Babel.

bash-3.2$ /usr/bin/python2.7 -c "import sys; print sys.path; import
numpy">  /tmp/out1
bash-3.2$ /usr/bin/python -c "import sys; print sys.path; import numpy"
bash-3.2$ cat /tmp/out1
'/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7', '/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/plat-darwin',
bash-3.2$ diff /tmp/out1 /tmp/out2
bash-3.2$ ls -al /usr/bin/python2.7
lrwxr-xr-x  1 root  wheel  75 Aug 23 11:10 /usr/bin/python2.7 ->

Presumably, this C program that uses dlopen(), Py_Initialize, and
Py_SimpleString should have exactly the same output.

/** foo.c */

main(int argc, char **argv)
 // void *lptr =
dlopen("/System/Library/Frameworks/Python.framework/Python", RTLD_NOW |
 void *lptr =
 if (lptr) {
   void (*pyinit)(void) = dlsym(lptr, "Py_Initialize");
   if (pyinit) {
     int (*runSimple)(const char *);
     (*pyinit)();              /* initialize Python */
     runSimple = dlsym(lptr, "PyRun_SimpleString");
     if (runSimple) {
       (*runSimple)("import sys ; print sys.path; import numpy");
   else {
     fprintf(stderr, "Unable to locate Py_Initialize: %s\n", dlerror());
 else {
   fprintf(stderr, "Error loading Python shared library: %s\n",

bash-3.2$ gcc foo.c ; ./a.out
['/usr/lib/', '/usr/lib/python2.7',
'/usr/lib/python2.7/plat-darwin', '/usr/lib/python2.7/plat-mac',
'/usr/Extras/lib/python', '/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload']
Traceback (most recent call last):
 File "<string>", line 1, in<module>
ImportError: No module named numpy

However as you see, it has a completely different sys.path. I can't seem
to find a way to get it to initialize Python with the same sys.path. It
seems like the libpython2.7.dylib is broken. I am at a loss on how to
fix this or even who to ask for help.
Date User Action Args
2012-10-26 09:17:32ronaldoussorensetrecipients: + ronaldoussoren, ned.deily
2012-10-26 09:17:32ronaldoussorensetmessageid: <>
2012-10-26 09:17:32ronaldoussorenlinkissue15498 messages
2012-10-26 09:17:31ronaldoussorencreate