[issue29309] Interpreter hang when interrupting a loop.run_in_executor() future

2021-12-06 Thread Irit Katriel
Irit Katriel added the comment: @asyncio.coroutine was removed in 3.10, and the run_in_executor.py doesn't run with async def because that does not allow yield. I'll close this as out of date, please create a new issue if you are still having a related problem with async def. --

[issue29309] Interpreter hang when interrupting a loop.run_in_executor() future

2017-01-19 Thread Rémi Cardona
Changes by Rémi Cardona : -- nosy: +RemiCardona ___ Python tracker ___ ___ Python-bugs-list

[issue29309] Interpreter hang when interrupting a loop.run_in_executor() future

2017-01-18 Thread Romain Sébille
Romain Sébille added the comment: Ok, thanks for the explanation! One thing still bother me, run_in_executor() allow us to launch blocking operations but without blocking the main thread, so there is a high chance that we wait inside one of the pool's worker. Does this mean run_in_executor()

[issue29309] Interpreter hang when interrupting a loop.run_in_executor() future

2017-01-18 Thread STINNER Victor
STINNER Victor added the comment: Sending SIGTERM (CTRL+c, KeyboardInterrupt) while Python is waiting in threading.Thread.join() is not supported. You have a thread running time.sleep(1). On Linux, this function calls the select() syscall. So you have the main thread waiting for the thread

[issue29309] Interpreter hang when interrupting a loop.run_in_executor() future

2017-01-18 Thread Romain Sébille
New submission from Romain Sébille: Hi, I stumble on this today and can't find any reasons or previous issue as to why this happen so I thought of submitting the issue here. I attached a script (run_in_executor.py) to reproduce the problem, the original problem arise when waiting to read on