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 djmdjm
Recipients aimacintyre, djmdjm, jnoller
Date 2008-09-19.20:20:08
SpamBayes Score 0.0004823362
Marked as misclassified No
Message-id <>
In-reply-to <>
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, but multiprocessing/
unconditionally depends on its presence.

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

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

Date User Action Args
2008-09-19 20:20:10djmdjmsetrecipients: + djmdjm, aimacintyre, jnoller
2008-09-19 20:20:09djmdjmlinkissue3770 messages
2008-09-19 20:20:08djmdjmcreate