[issue3375] _multiprocessing.so build problems

Guido van Rossum <[EMAIL PROTECTED]> added the comment: I've checked in a fix (r65063) that simply clear sys.path_importer_cache right before the attempted import of the freshly-built extension. This seems to work. -- assignee: jnoller -> gvanrossum resolution: -> fixed status: open ->

[issue3375] _multiprocessing.so build problems

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: How about simply doing sys.path_importer_cache.clear() at the right point in setup.py? I don't think the performance loss would be overwhelming... -- nosy: +pitrou ___ Python tracker <[EMAIL PROTEC

[issue3375] _multiprocessing.so build problems

Guido van Rossum <[EMAIL PROTECTED]> added the comment: The order thing was a red herring. However, I understand what's going on now. Somebody else can fix it hopefully. So what's going on: In the Python instance that runs setup.py, importing _multiprocessing fails. But if I start a new Pyth

[issue3375] _multiprocessing.so build problems

Guido van Rossum <[EMAIL PROTECTED]> added the comment: Here is the output of python -v during "import _multiprocessing". Maybe this gives someone a clue? >>> import _multiprocessing dlopen("/Users/guido/p3/build/lib.macosx-10.3-i386-3.0/_multiprocessing.so", 2); # /Users/guido/p3/Lib/pickle.pyc

[issue3375] _multiprocessing.so build problems

Guido van Rossum <[EMAIL PROTECTED]> added the comment: When a second 'make' fixes things, that usually means that there's a dependency on another extension that is built later in the normal build sequence. I vaguely we had this before and fixed it by reordering things. Grepping the sources of _

[issue3375] _multiprocessing.so build problems

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Okay, I have more information, but still no diagnosis. I stuck a 'raise' in the setup.py so that when the ImportError occurs, it doesn't get swallowed. Instead it stops the build process in its tracks. The attached file contains the releva

[issue3375] _multiprocessing.so build problems

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- assignee: -> jnoller ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue3375] _multiprocessing.so build problems

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: py3k. i think the thing to do is to try to figure out why the import is failing even though the compilation appears to succeed. it's the suppressed import error that's going to be the clue. ___ Python tr

[issue3375] _multiprocessing.so build problems

Jesse Noller <[EMAIL PROTECTED]> added the comment: Even with that output it's not clear what's happening during the compile step. Barry - is this on trunk and py3k? ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3375] _multiprocessing.so build problems

Jesse Noller <[EMAIL PROTECTED]> added the comment: Andrii gave me make -d output with the failure: building '_multiprocessing' extension creating build/temp.linux-i686- 3.0/home/mishok/doc/python/tmp/py3k/Modules/_multiprocessing gcc -pthread -fPIC -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -

[issue3375] _multiprocessing.so build problems

Andrii V. Mishkovskyi <[EMAIL PROTECTED]> added the comment: Attached the log of 'make -d' on clean checkout of py3k branch. This is on Ubuntu 8.04.1. -- nosy: +mishok13 Added file: http://bugs.python.org/file10907/make-d.log.bz2 ___ Python tracker <[

[issue3375] _multiprocessing.so build problems

Jesse Noller <[EMAIL PROTECTED]> added the comment: Barry, I can't seem to repro this against trunk on both my Ubuntu and OS/X machines. If you get a chance, can you see if you can get the output from a make -d? ___ Python tracker <[EMAIL PROTECTED]>

[issue3375] _multiprocessing.so build problems

Jesse Noller <[EMAIL PROTECTED]> added the comment: I'll try with a clean tree, but I've seen this before and I'm quite mystified. -- nosy: +jnoller ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3375] _multiprocessing.so build problems

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- dependencies: +test_multiprocessing hangs intermittently on POSIX platforms ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3375] _multiprocessing.so build problems

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: Er, make that bug 3088 ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mai

[issue3375] _multiprocessing.so build problems

New submission from Barry A. Warsaw <[EMAIL PROTECTED]>: _multiprocessing.so has build problems on both OS X 10.5 and Ubuntu Linux 8.04. It's very strange though because there are no apparent errors in compilation, however when the build process tries to import the module, that fails and it gets