Message 415415 - 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.

Author	asvetlov
Recipients	asvetlov, synchronizing, yselivanov
Date	2022-03-17.15:09:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1647529745.58.0.775674643893.issue43019@roundup.psfhosted.org>
In-reply-to

Content
Threads are not interruptable in Python. The same for concurrent.future executor. asyncio and `wait_for` is not special. I'm not sure should we document it and if yes -- where should we do it? Adding a note to every function could be cumbersome.

Threads are not interruptable in Python.
The same for concurrent.future executor.
asyncio and `wait_for` is not special.

I'm not sure should we document it and *if* yes -- where should we do it?

Adding a note to every function could be cumbersome.

History
Date	User	Action	Args
2022-03-17 15:09:05	asvetlov	set	recipients: + asvetlov, yselivanov, synchronizing
2022-03-17 15:09:05	asvetlov	set	messageid: <1647529745.58.0.775674643893.issue43019@roundup.psfhosted.org>
2022-03-17 15:09:05	asvetlov	link	issue43019 messages
2022-03-17 15:09:05	asvetlov	create