[issue31357] Expose `worker_target` and `workitem_cls` as arugments to customize `ThreadPoolExecutor` behaviour

[Irit Katriel]

Change by Irit Katriel :


--
type: behavior -> enhancement

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue31357] Expose `worker_target` and `workitem_cls` as arugments to customize `ThreadPoolExecutor` behaviour

[SenbinYu]

New submission from SenbinYu:

With the two arguments, we can esaily to customize behaviour when I submit task 
to a ThreadPoolExecutor instance. It's more useful when I want to execute 
coroutine function with this executor.


With this, we can run coroutine in any pattern programs and don't care about 
whether the main framework supports. Also, in mamy non asynchronous web 
application, we can use asyncio releated features in this way. I think people 
will like this. Although, I can write an another ThreadPoolExecutor, but I 
think we should reuse as more code in standard lib as we can. Lastly, this 
makes ThreadPoolExecutor more flexible.

--
components: Library (Lib)
messages: 301414
nosy: justdoit0823
priority: normal
pull_requests: 3381
severity: normal
status: open
title: Expose `worker_target` and `workitem_cls` as arugments to customize 
`ThreadPoolExecutor` behaviour
type: behavior
versions: Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com