Message 345681 - Python tracker

➜

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	<[email protected]>
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).

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:17	crusaderky	set	recipients: + crusaderky, eric.snow
2019-06-15 13:15:17	crusaderky	set	messageid: <[email protected]>
2019-06-15 13:15:17	crusaderky	link	issue37293 messages
2019-06-15 13:15:17	crusaderky	create