[issue33823] A BUG in concurrent/asyncio

Terry J. Reedy added the comment: Python++, when you respond by email, rather than on the web form, delete the message you are responding to. It is already present on the web page and should not be repeated. I unlinked msg319278 because it uselessly repeats the same message that it

[issue33823] A BUG in concurrent/asyncio

Change by Terry J. Reedy : -- Removed message: https://bugs.python.org/msg319278 ___ Python tracker ___ ___ Python-bugs-list

[issue33823] A BUG in concurrent/asyncio

Pablo Galindo Salgado added the comment: Python++: Sorry, I still cannot understand exactly what is wrong. Could you please redact a little paragraph explaining (1) what function/functions are you using (and maybe a very short example), (2) what is not working and (3) what do you expect to

[issue33823] A BUG in concurrent/asyncio

Python++ added the comment: First Kind of resutl sets: = Process-2:<4816> is ProcessExecuting [0] MainThread:<4816> is ThreadExecuting [0] exe_iter:0 sub_iter:0 Run for Wheel and result:0 callback number:1 MainThread:<4816> is

[issue33823] A BUG in concurrent/asyncio

Python++ added the comment: First Kind of resutl sets: = Process-2:<4816> is ProcessExecuting [0] MainThread:<4816> is ThreadExecuting [0] exe_iter:0 sub_iter:0 Run for Wheel and result:0 callback number:1 MainThread:<4816> is

[issue33823] A BUG in concurrent/asyncio

Yury Selivanov added the comment: > which results in the resulting statistics of the last code run cannot be > promised to be separated. I'm sorry but I cannot parse your message and the attached code snippet. Please try to formulate the actual bug/feature request more clearly. --

[issue33823] A BUG in concurrent/asyncio

Change by Python++ : Added file: https://bugs.python.org/file47637/BUG for concurrent.futures(Found by william).py ___ Python tracker ___

[issue33823] A BUG in concurrent/asyncio

New submission from Python++ : ProcessPoolExecutor cannot specify the number of cores when running the Muti-Sub Event Loops, which results in the resulting statistics of the last code run cannot be promised to be separated. I'm deep hoping some genius can propose a solution and fix these