You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree, however, I don't really see the point of changing the start method in loky.
I think I would favor:
not implying that this is public API by deleting the section mentioning set_start_method in the API doc;
deprecating the old "loky_init_main" start method, which is probably useless nowadays.
Similarly, now that cloudpickle is based the C-implementation of pickle, it is almost always as fast as the "pickle" module and our documentation, the narrative of this example has become meaningless:
As this library is slower than the pickle module in the standard library, by default, loky uses it only to serialize objects which are detected to be in the main module.
There is no speed tradeoff anymore;
I cannot see in the code where we would restrict the use of cloudpickle to only things defined in __main__. I think we use it for everything, e.g. non-picklable locally defined functions:
but the actual API seems to be
loky.backend.context.set_start_method
The text was updated successfully, but these errors were encountered: