New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
_multiprocessing.so build problems #47625
Comments
_multiprocessing.so has build problems on both OS X 10.5 and Ubuntu Sorry, I have no more clues than that, but see also but 3088. |
Er, make that bug 3088 |
I'll try with a clean tree, but I've seen this before and I'm quite |
Barry, I can't seem to repro this against trunk on both my Ubuntu and OS/X |
Attached the log of 'make -d' on clean checkout of py3k branch. This is |
Andrii gave me make -d output with the failure: building '_multiprocessing' extension |
Even with that output it's not clear what's happening during the compile |
py3k. i think the thing to do is to try to figure out why the import is |
Okay, I have more information, but still no diagnosis. I stuck a |
When a second 'make' fixes things, that usually means that there's a Grepping the sources of _multiprocessing for Import, I wonder if it |
Here is the output of python -v during "import _multiprocessing". Maybe >>> import _multiprocessing
dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_multiprocessing.so",
2);
# /Users/guido/p3/Lib/pickle.pyc matches /Users/guido/p3/Lib/pickle.py
import pickle # precompiled from /Users/guido/p3/Lib/pickle.pyc
import marshal # builtin
# /Users/guido/p3/Lib/struct.pyc matches /Users/guido/p3/Lib/struct.py
import struct # precompiled from /Users/guido/p3/Lib/struct.pyc
dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_struct.so", 2);
import _struct # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_struct.so
dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/binascii.so", 2);
import binascii # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/binascii.so
dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_pickle.so", 2);
import _pickle # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_pickle.so
import multiprocessing # directory /Users/guido/p3/Lib/multiprocessing
# /Users/guido/p3/Lib/multiprocessing/__init__.pyc matches
/Users/guido/p3/Lib/multiprocessing/__init__.py
import multiprocessing # precompiled from
/Users/guido/p3/Lib/multiprocessing/__init__.pyc
# /Users/guido/p3/Lib/multiprocessing/process.pyc matches
/Users/guido/p3/Lib/multiprocessing/process.py
import multiprocessing.process # precompiled from
/Users/guido/p3/Lib/multiprocessing/process.pyc
dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/itertools.so", 2);
import itertools # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/itertools.so
import _multiprocessing # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_multiprocessing.so
import _multiprocessing # dynamically loaded from
/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_multiprocessing.so
>>> |
The order thing was a red herring. However, I understand what's going So what's going on: In the Python instance that runs setup.py, I found this by (a) disabling the two except clauses in setup.py that Good luck fixing... |
How about simply doing sys.path_importer_cache.clear() at the right |
I've checked in a fix (r65063) that simply clear sys.path_importer_cache |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: