[issue14456] Relation between threads and signals unclear

2016-04-10 Thread Roundup Robot
Roundup Robot added the comment: New changeset 73050563053f by Martin Panter in branch '3.5': Issue #14456: Remove contradiction about blocking signals from bad merge https://hg.python.org/cpython/rev/73050563053f New changeset a8dbe6016a31 by Martin Panter in branch 'default': Issue #14456: Mer

[issue14456] Relation between threads and signals unclear

2012-03-31 Thread Sven Marnach
Sven Marnach added the comment: Thanks, Antoine! It's perfectly clear now, and the newly introduces headlines are a definite improvement. -- ___ Python tracker ___ ___

[issue14456] Relation between threads and signals unclear

2012-03-31 Thread Antoine Pitrou
Antoine Pitrou added the comment: Should be fixed now. -- nosy: +pitrou resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue14456] Relation between threads and signals unclear

2012-03-31 Thread Roundup Robot
Roundup Robot added the comment: New changeset 52e32f3b933d by Antoine Pitrou in branch '3.2': Issue #14456: improve documentation of the signal module w.r.t. threads. http://hg.python.org/cpython/rev/52e32f3b933d New changeset 44d13f371811 by Antoine Pitrou in branch 'default': Issue #14456: i

[issue14456] Relation between threads and signals unclear

2012-03-30 Thread STINNER Victor
STINNER Victor added the comment: > These two passages are in contradiction to each other. By default, a thread signal can receive any signal and the signal handler implemented in C will be called in the context of the thread. CPython ensures that a signal handler implemented in Python and in

[issue14456] Relation between threads and signals unclear

2012-03-30 Thread Sven Marnach
Sven Marnach added the comment: For reference: the functions 'pthread_kill()' etc. were intrduced in issue8407. -- ___ Python tracker ___ ___

[issue14456] Relation between threads and signals unclear

2012-03-30 Thread Sven Marnach
New submission from Sven Marnach : The documentation of the 'signal' module states on the one hand [T]he 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 individ