always serialize the function using cloudpickle #281
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This was a suggestion of @jbweston some time ago.
Using this, the learners are picklable regardless of the serialization package chosen.
This also means that we can e.g. use lambda functions when using a
ProcessPoolExecutor
and do not needloky
per se.I am making these changes now because I am finding that in some cases it's not preferable to use
cloudpickle
to serialize simple dictionaries (see cloudpipe/cloudpickle#375).Checklist
pre-commit run --all
(first install usingpip install pre-commit
)pytest
passedType of change
Check relevant option(s).