Skip to content

concurrent.futures.InterpreterPoolExecutor #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
crusaderky opened this issue Jun 12, 2019 · 2 comments
Closed

concurrent.futures.InterpreterPoolExecutor #45

crusaderky opened this issue Jun 12, 2019 · 2 comments

Comments

@crusaderky
Copy link

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 pull request to CPython as soon as #34 is resolved (it's kinda pointless before that).

@ericsnowcurrently
Copy link
Owner

Whoa, that's really cool! :) I have talked briefly with Davin Potts about integrating subinterpreters into multiprocessing, but hadn't thought about concurrent.futures. So thanks for looking into this.

I recommend opening an issue on bugs.python.org for this as soon as it makes sense. This repo is unofficial, effectively just a planning tool with a specific goal in mind, and mostly just me. :) The official BPO tracker is where the real collaboration happens. So I'd hate for your work to not get enough attention.

FWIW, I am keeping track of a few things that I hope to work on after PEP 554 is landed, but mostly everything here is targeting the minimal functionality to hit the core goal. :)

@ericsnowcurrently
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants