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 exarkun
Recipients exarkun, loewis, marcin.bachry, pitrou, spiv
Date 2010-05-01.15:22:03
SpamBayes Score 0.00361678
Marked as misclassified No
Message-id <>
One open question regarding interaction with threading.  sigprocmask's behavior in a multithreaded program is unspecified.  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.  I don't see any disadvantages of doing the latter, and the former seems like it would create an attractive nuisance.  However, I don't have much experience with sigprocmask; I'm only interested in it because of its use in combination with signalfd.
Date User Action Args
2010-05-01 15:22:05exarkunsetrecipients: + exarkun, loewis, spiv, pitrou, marcin.bachry
2010-05-01 15:22:05exarkunsetmessageid: <>
2010-05-01 15:22:03exarkunlinkissue8407 messages
2010-05-01 15:22:03exarkuncreate