[issue37293] concurrent.futures.InterpreterPoolExecutor

Change by jakirkham : -- nosy: +jakirkham ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37293] concurrent.futures.InterpreterPoolExecutor

Eric Snow added the comment: @Davin, we've spoken before about something similar for multiprocessing, IIRC. :) -- nosy: +davin ___ Python tracker ___

[issue37293] concurrent.futures.InterpreterPoolExecutor

Eric Snow added the comment: FWIW, performance benefits when subinterpreters stop sharing the GIL are not the only benefit. In fact, PEP 554 is specifically written to avoid that consideration, focusing on the benefits of the concurrency model (i.e. CSP). So I wouldn't call this pointless

[issue37293] concurrent.futures.InterpreterPoolExecutor

New submission from Crusader Ky : As one of the logical consequences to PEP 554, it would be neat to have a concurrent.futures.InterpreterPoolExecutor. I wrote the initial code at https://github.com/crusaderky/subinterpreters_tests - currently missing unit tests and pickle5 buffers support.