Message105099
> 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. |
|
Date |
User |
Action |
Args |
2010-05-05 22:27:43 | pitrou | set | recipients:
+ pitrou, loewis, gregory.p.smith, spiv, exarkun, marcin.bachry |
2010-05-05 22:27:43 | pitrou | set | messageid: <1273098463.61.0.760412096962.issue8407@psf.upfronthosting.co.za> |
2010-05-05 22:27:42 | pitrou | link | issue8407 messages |
2010-05-05 22:27:41 | pitrou | create | |
|