-
Notifications
You must be signed in to change notification settings - Fork 101
Why do we use multiprocess instead of multiprocessing #60
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
Comments
Just to clarify you mean what are the differences between multiprocess (https://github.com/uqfoundation/multiprocess) and multiprocessing (https://docs.python.org/2/library/multiprocessing.html) ? |
Yes, exactly -- I think I depended on multiprocess out of habit / it used to be the only game in town, but if we can get away with the (built-in) multiprocessing, all the better! |
It looks like there are some specific new features it adds (from the readme below). If we dont use these features we should use the builtin one
|
It's not clear to me that these are features only of |
I think we are both agreeing on the point that we use the inbuilt library until we run out of features from it :) You can probably edit this issue title to be 'Use multiprocessing from standard library' ? |
This seems like an unnecessary dependency given that we just 1. use it in the stand-alone mode and 2. I think
multiprocessing
provides all the same functionality? I'm still not sure what the multiprocess fork actually does.The text was updated successfully, but these errors were encountered: