Message 376394 - 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	wocket
Recipients	methane, vstinner, wocket
Date	2020-09-04.18:55:50
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1599245750.25.0.932652081882.issue41710@roundup.psfhosted.org>
In-reply-to

Content
sys.thread_info = sys.thread_info(name='pthread', lock='semaphore', version='NPTL 2.31') on my system. Looking at the source I think the semaphore implementation will be used on all modern Linux systems. In my tests it works as expected on a Macintosh (3.8.5 with lock='mutex+cond') and also if I force a Linux build to use the mutex+cond implementation by defining HAVE_BROKEN_POSIX_SEMAPHORES. Doesn't look like those glibc and Linux bug reports will get any attention anytime soon. I will find a workaround instead :-/

sys.thread_info = sys.thread_info(name='pthread', lock='semaphore', version='NPTL 2.31') on my system. Looking at the source I think the semaphore implementation will be used on all modern Linux systems.

In my tests it works as expected on a Macintosh (3.8.5 with lock='mutex+cond') and also if I force a Linux build to use the mutex+cond implementation by defining HAVE_BROKEN_POSIX_SEMAPHORES.

Doesn't look like those glibc and Linux bug reports will get any attention anytime soon. I will find a workaround instead :-/

History
Date	User	Action	Args
2020-09-04 18:55:50	wocket	set	recipients: + wocket, vstinner, methane
2020-09-04 18:55:50	wocket	set	messageid: <1599245750.25.0.932652081882.issue41710@roundup.psfhosted.org>
2020-09-04 18:55:50	wocket	link	issue41710 messages
2020-09-04 18:55:50	wocket	create