Message 383734 - Python tracker

Message383734

Author	AR-Kareem
Recipients	AR-Kareem, eryksun
Date	2020-12-25.11:03:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1608894238.53.0.777179576277.issue42730@roundup.psfhosted.org>
In-reply-to

Content
Shouldn't the behaviour for _thread.interrupt_main() be always to interrupt the main thread. I would expect that if a child thread uses _thread.interrupt_main() that the main thread be interrupted regardless of how the python script was invoked. Wouldn't it be more reasonable to make _thread.interrupt_main() always raise a SIGINT? I'm not sure if this is technically considered a bug or not, but it seems that it's not functioning as intended even in Python 3.7

Content

Shouldn't the behaviour for _thread.interrupt_main() be always to interrupt the main thread. 

I would expect that if a child thread uses _thread.interrupt_main() that the main thread be interrupted regardless of how the python script was invoked.

Wouldn't it be more reasonable to make _thread.interrupt_main() always raise a SIGINT? I'm not sure if this is technically considered a bug or not, but it seems that it's not functioning as intended even in Python 3.7

History
Date	User	Action	Args
2020-12-25 11:03:58	AR-Kareem	set	recipients: + AR-Kareem, eryksun
2020-12-25 11:03:58	AR-Kareem	set	messageid: <1608894238.53.0.777179576277.issue42730@roundup.psfhosted.org>
2020-12-25 11:03:58	AR-Kareem	link	issue42730 messages
2020-12-25 11:03:58	AR-Kareem	create