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 exarkun, gregory.p.smith, loewis, marcin.bachry, pitrou, spiv
Date 2010-05-05.22:27:41
SpamBayes Score 0.012400781
Marked as misclassified No
Message-id <1273098463.61.0.760412096962.issue8407@psf.upfronthosting.co.za>
In-reply-to
Content
> pthread_sigmask should be used instead.  I could either expose both of > these and let the caller choose, or I could make signal.sigprocmask use > pthread_sigmask if it's available, and fall back to sigprocmask.

Or perhaps you could disable the feature if pthread_sigmask isn't available. Apparently, FreeBSD and Mac OS X have it, as well as Linux.
History
Date User Action Args
2010-05-05 22:27:43pitrousetrecipients: + pitrou, loewis, gregory.p.smith, spiv, exarkun, marcin.bachry
2010-05-05 22:27:43pitrousetmessageid: <1273098463.61.0.760412096962.issue8407@psf.upfronthosting.co.za>
2010-05-05 22:27:42pitroulinkissue8407 messages
2010-05-05 22:27:41pitroucreate