Message 73440 - Python tracker
Message73440
| Author | djmdjm |
|---|---|
| Recipients | aimacintyre, djmdjm, jnoller |
| Date | 2008-09-19.20:20:08 |
| SpamBayes Score | 0.0004823362 |
| Marked as misclassified | No |
| Message-id | <alpine.BSO.1.10.0809200617000.3881@fuyu.mindrot.org> |
| In-reply-to | <1220487838.93.0.477905681389.issue3770@psf.upfronthosting.co.za> |
| Content | |
|---|---|
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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-09-19 20:20:10 | djmdjm | set | recipients: + djmdjm, aimacintyre, jnoller |
| 2008-09-19 20:20:09 | djmdjm | link | issue3770 messages |
| 2008-09-19 20:20:08 | djmdjm | create | |