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 pitrou
Recipients beazley, dabeaz, flox, kristjan.jonsson, loewis, pitrou, techtonik, torsten
Date 2010-04-15.16:48:38
SpamBayes Score 1.5706874e-07
Marked as misclassified No
Message-id <1271350242.3425.21.camel@localhost>
In-reply-to <1271349284.96.0.5465077793.issue8299@psf.upfronthosting.co.za>
Content
> Yes, we put #error in both places (defining and undefining
> USE_SEMAPHORES).  The colleague in question is Christian Tismer, he is
> unlikely to have gotten it wrong.

Ok, so can you or Christian open an issue about it? We should try to fix
it.

> I am also curious why David Beazley kept talking about the "binary
> semaphore" when it is apparent that that is supposed to be a "hack" to
> use on platforms that don't have posix semaphores.

I think David often uses technical terms (such as "semaphore" or
"signal") in more generic meanings than what you might expect :)
History
Date User Action Args
2010-04-15 16:48:39pitrousetrecipients: + pitrou, loewis, beazley, kristjan.jonsson, techtonik, flox, dabeaz, torsten
2010-04-15 16:48:38pitroulinkissue8299 messages
2010-04-15 16:48:38pitroucreate