[issue3770] test_multiprocessing fails on systems with HAVE_SEM_OPEN=0

[Damien Miller]

Damien Miller <djmdjm at users.sourceforge.net> added the comment:

So the bug is actually in the multiprocessing module rather than the
unittest. If HAVE_SEM_OPEN is not defined then SemLock is never
built into _multiprocessing.so, but multiprocessing/syncronize.py
unconditionally depends on its presence.

I guess _multiprocessing could always define a dummy SemLock or
synchronize.py could check before it depends on it.

(it would be great to see this fixed for 2.6)

-d

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3770>
_______________________________________