Message 388972 - Python tracker

➜

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.

In-reply-to
Author	eryksun
Recipients	AR-Kareem, eryksun
Date	2021年03月17日.21:45:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1616017501.5.0.906359077597.issue42730@roundup.psfhosted.org>

Content
> Shouldn't the behaviour for _thread.interrupt_main() be always to > interrupt the main thread. The underlying C API function, PyErr_SetInterrupt(), simulates SIGINT without actually sending the signal to the process via kill() or raise(), but the doc string of interrupt_main() doesn't explain this, or at least it didn't used to. bpo-43356 generalized _thread.interrupt_main() to support simulating any available signal, and hopefully the new doc string [1] clarifies the intent. --- [1] https://github.com/python/cpython/blob/9976834f807ea63ca51bc4f89be457d734148682/Modules/_threadmodule.c#L1194

Content

> Shouldn't the behaviour for _thread.interrupt_main() be always to 
> interrupt the main thread. 
The underlying C API function, PyErr_SetInterrupt(), simulates SIGINT without actually sending the signal to the process via kill() or raise(), but the doc string of interrupt_main() doesn't explain this, or at least it didn't used to. bpo-43356 generalized _thread.interrupt_main() to support simulating any available signal, and hopefully the new doc string [1] clarifies the intent.
---
[1] https://github.com/python/cpython/blob/9976834f807ea63ca51bc4f89be457d734148682/Modules/_threadmodule.c#L1194

History
Date	User	Action	Args
2021年03月17日 21:45:01	eryksun	set	recipients: + eryksun, AR-Kareem
2021年03月17日 21:45:01	eryksun	set	messageid: <1616017501.5.0.906359077597.issue42730@roundup.psfhosted.org>
2021年03月17日 21:45:01	eryksun	link	issue42730 messages
2021年03月17日 21:45:01	eryksun	create

homepage