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 movement
Recipients Rhamphoryncus, bamby, exarkun, gvanrossum, laca, movement, mstepnicki, pitrou, ross
Date 2009-12-14.18:52:18
SpamBayes Score 0.000534507
Marked as misclassified No
Message-id <>
The spec broken is here:


# Some care must be taken if both signals and threads are used in the
same program. The fundamental thing to remember in using signals and
threads simultaneously is: always perform signal() operations in the
main thread of execution. Any thread can perform an alarm(),
getsignal(), pause(), setitimer() or getitimer(); only the main thread
can set a new signal handler, and the main thread will be the only one
to receive signals (this is enforced by the Python signal module, even
if the underlying thread implementation supports sending signals to
individual threads). This means that signals can’t be used as a means of
inter-thread communication. Use locks instead.
Date User Action Args
2009-12-14 18:52:19movementsetrecipients: + movement, gvanrossum, exarkun, Rhamphoryncus, pitrou, ross, bamby, laca, mstepnicki
2009-12-14 18:52:19movementsetmessageid: <>
2009-12-14 18:52:18movementlinkissue1975 messages
2009-12-14 18:52:18movementcreate