Message 73918 - Python tracker

➜

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	ncoghlan
Recipients	aimacintyre, djmdjm, jnoller, ncoghlan
Date	2008-09-27.02:51:29
SpamBayes Score	0.00021839672
Marked as misclassified	No
Message-id	<1222483890.46.0.536317141973.issue3770@psf.upfronthosting.co.za>
In-reply-to

Content
Looking at mp.synchronize, the whole module really does depend on a working _multiprocessing.SemLock instance. If these platforms don't have a native semaphore implementation, what is their basic inter-process synchronisation primitive? Once that is identified, then it should be possible to code either a C or Python semaphore implementation based on that primitive.

Looking at mp.synchronize, the whole module really does depend on a
working _multiprocessing.SemLock instance. If these platforms don't have
a native semaphore implementation, what is their basic inter-process
synchronisation primitive?

Once that is identified, then it should be possible to code either a C
or Python semaphore implementation based on that primitive.

History
Date	User	Action	Args
2008-09-27 02:51:30	ncoghlan	set	recipients: + ncoghlan, aimacintyre, djmdjm, jnoller
2008-09-27 02:51:30	ncoghlan	set	messageid: <1222483890.46.0.536317141973.issue3770@psf.upfronthosting.co.za>
2008-09-27 02:51:29	ncoghlan	link	issue3770 messages
2008-09-27 02:51:29	ncoghlan	create