Skip to content

Conversation

@lgray
Copy link
Collaborator

@lgray lgray commented Nov 1, 2025

Fixes #1408

@nsmith-
Copy link
Member

nsmith- commented Nov 1, 2025

Can add Iason's test as well

@ikrommyd
Copy link
Collaborator

ikrommyd commented Nov 1, 2025

Thanks! I was not aware that you can subclass the process pool like that and define your pickler.

@lgray
Copy link
Collaborator Author

lgray commented Nov 1, 2025

@nsmith- Yeah I'll add Iason's test once the baseline tests go. I probably typo'd something. Figured out a better way to set the pickler that makes fewer assumptions, added test.

@lgray
Copy link
Collaborator Author

lgray commented Nov 1, 2025

Eh lots of stuff failing - I'll get it figured out.

@lgray lgray force-pushed the lgray/cloudpicklefutures branch from 3729aa1 to 3259acd Compare November 3, 2025 03:38
@nsmith-
Copy link
Member

nsmith- commented Nov 3, 2025

If this doesn't pan out, another more brute-force option would be to create a payload wrapper that uses cloudpickle to serialize the actual work function and then give that to the process pool.

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

Successfully merging this pull request may close these issues.

Can't use a lambda function in iteritems_options with FuturesExecutor

4 participants