[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

Change by Ronald Oussoren : -- resolution: -> not a bug type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

Change by Jeffrey Kintscher : -- nosy: -Jeffrey.Kintscher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

Change by KevinGuo : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

KevinGuo added the comment: OK, thanks for your reply -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

Ronald Oussoren added the comment: This is expected behaviour. Run_in_executor uses a concurrent.futures.ThreadPoolExecutor to manage the worker threads. Those threads will get reused when more work is scheduled, and will exit when the runloop is shut down. -- nosy: +ronaldoussoren

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

Change by Jeffrey Kintscher : -- nosy: +Jeffrey.Kintscher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41456] loop.run_in_executor creat thread but not destory it after the task run over

New submission from Guo Xiyong : code like this: import asyncio import time import threading def sync_test(): time.sleep(1) async def run_test(): loop = asyncio.get_event_loop() for _ in range(10): # r = await loop.getaddrinfo('wq.io', 443) # print(r)