Tangellapalli Sai Hanuma Rahul added the comment:
Yes, it's true, it's so naive method, Contextvars! may be inside the Future
Object?
--
resolution: -> rejected
stage: patch review -> resolved
status: open -> closed
___
Python tracke
Tangellapalli Sai Hanuma Rahul added the comment:
In summary;
==
Current Problem:
--
ThreadPoolExecutor handles all threads-related activities so the user needs to
just submit tasks and set max_workers and other Executor settings if necessary.
If ThreadPoolExecutor
Tangellapalli Sai Hanuma Rahul added the comment:
There is a new function submit_with_name in _base.Executor that can accept name
parameters before args and kwargs, submit can continue to be used as before.
submit internally calls submit_with_name with name as None. Calling
submit_with_name
Tangellapalli Sai Hanuma Rahul added the comment:
ThreadPool handles tasks concurrently through Threads so users need not worry
about the creation/deletion of Threads, it uses reuses threads whenever
possible and it can handle any tasks.
However, it should be possible for users to at least
Change by Tangellapalli Sai Hanuma Rahul :
--
versions: -Python 3.10, Python 3.11
___
Python tracker
<https://bugs.python.org/issue45689>
___
___
Python-bug
Change by Tangellapalli Sai Hanuma Rahul :
--
hgrepos: -410
___
Python tracker
<https://bugs.python.org/issue45689>
___
___
Python-bugs-list mailing list
Unsub
Change by Tangellapalli Sai Hanuma Rahul :
--
hgrepos: +410
keywords: +patch
pull_requests: +27619
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/29359
___
Python tracker
<https://bugs.python.org/issu
New submission from Tangellapalli Sai Hanuma Rahul :
Feature Request:
Where we can use custom Names for separate threads submitted in
ThreadPoolExecutor.
It achieves by sending the name string to _work_queue of ThreadPoolExecutor and
then in _worker function modifies the name
