Skip to content
Discussion options

You must be logged in to vote

I tried this locally and can confirm I'm getting the same error. I admit when I added the process executor, I didn't really test it -- it was just something Python supported so I added it without much further though.

I think given the limitations of what can be pickled that it won't be possible to use future, future-call, bound-fn*, or bound-fn with a process pool executor. They create anonymous functions which contain the state of the current thread bindings, so my guess is there's not really any way of recreating that functionality using pickle (which is how concurrent.futures.ProcessPoolExecutor works).

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@chrisrink10
Comment options

Answer selected by chrisrink10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants