long_callback: Switch from FlaskCaching to Diskcache and add windows support #32
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.
This PR adds Windows support for
long_callback
.This primarily involved two changes:
multiprocess
library for running the background processes on Windows. This is an API compatible alternative to the built-in Pythonmultiprocessing
module that usesdill
for cross-process serialization (Rather than the built-inpickle
module). Unlike pickle,dill
can serializinglambda
functions and function closures. Serialization is not required at all on non-Windows platforms, so in these cases the regularmultiprocessing
module is used, and themultiprocess
package is not required.The documentation examples have been updated to remove the FlaskCaching backend, and replace it with the Diskcache backend. The Celery backend remains unchanged.