This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author crusaderky
Recipients crusaderky, eric.snow
Date 2019-06-15.13:15:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560604517.31.0.263744065617.issue37293@roundup.psfhosted.org>
In-reply-to
Content
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.

If everybody is happy with the design, I'll start working on a PR as soon as the GIL becomes per-interpreter (it's kinda pointless before that).
History
Date User Action Args
2019-06-15 13:15:17crusaderkysetrecipients: + crusaderky, eric.snow
2019-06-15 13:15:17crusaderkysetmessageid: <1560604517.31.0.263744065617.issue37293@roundup.psfhosted.org>
2019-06-15 13:15:17crusaderkylinkissue37293 messages
2019-06-15 13:15:17crusaderkycreate