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.

classification
Title: signal.siginterrupt description has typo
Type: enhancement Stage:
Components: Documentation Versions:
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Tom Meagher, docs@python, r.david.murray, vstinner
Priority: normal Keywords:

Created on 2015-11-05 16:54 by Tom Meagher, last changed 2022-04-11 14:58 by admin.

Messages (3)
msg254121 - (view) Author: Tom Meagher (Tom Meagher) Date: 2015-11-05 16:54
"if flag is False, system calls will be restarted when interrupted by signal signalnum, otherwise system calls will be interrupted."

This sentence doesn't make any sense as written.  I assume there should be a "not" in there somewhere, but I'm unclear if signal calls are not interrupted when the flag is false, or not interrupted when they are true.
msg254132 - (view) Author: R. David Murray (r.david.murray) * (Python committer) Date: 2015-11-05 17:49
The first phase says "restarted when interrupted", the second phrase says "interrupted".  So the difference is whether the system call is restarted or left in interrupted state (ie: the signal will propagate, which is confirmed by the second paragraph).  I can't see a way to phrase it any more clearly, can you?
msg254140 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2015-11-05 20:30
For more information on how Python handles signals, you can also read the PEP 475 (which changed how Python 3.5 handles signals ;-))
History
Date User Action Args
2022-04-11 14:58:23adminsetgithub: 69745
2015-11-05 20:30:22vstinnersetnosy: + vstinner
messages: + msg254140
2015-11-05 17:49:27r.david.murraysetnosy: + r.david.murray
messages: + msg254132
2015-11-05 16:54:37Tom Meaghercreate