Message 95548 - 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	jnoller
Recipients	db3l, jnoller, mark.dickinson
Date	2009-11-20.14:23:02
SpamBayes Score	0.007291386
Marked as misclassified	No
Message-id	<1258726984.56.0.193438139769.issue7272@psf.upfronthosting.co.za>
In-reply-to

Content
Thanks mark - if POSIX semaphores aren't available, we're largely dead- on-arrival. I thought FBSD was at the point of enabling them by default - boo on me. See also: http://bugs.python.org/issue3770#msg73958 and http://bugs.python.org/issue3770#msg83495 - with martin's help last pycon I cut a lot of the "HAVE_BROKEN..." values to autoconf checks in configure.in. I think the right way (however unpleasant) is to check to see if we have POSIX semaphores, period - if we don't, _multiprocessing should just not compile.

Thanks mark - if POSIX semaphores aren't available, we're largely dead-
on-arrival. I thought FBSD was at the point of enabling them by default 
- boo on me. See also: http://bugs.python.org/issue3770#msg73958 and 
http://bugs.python.org/issue3770#msg83495 - with martin's help last 
pycon I cut a lot of the "HAVE_BROKEN..." values to autoconf checks in 
configure.in.

I think the right way (however unpleasant) is to check to see if we have 
POSIX semaphores, period - if we don't, _multiprocessing should just not 
compile.

History
Date	User	Action	Args
2009-11-20 14:23:04	jnoller	set	recipients: + jnoller, db3l, mark.dickinson
2009-11-20 14:23:04	jnoller	set	messageid: <1258726984.56.0.193438139769.issue7272@psf.upfronthosting.co.za>
2009-11-20 14:23:03	jnoller	link	issue7272 messages
2009-11-20 14:23:02	jnoller	create