[issue18999] Robustness issues in multiprocessing.{get, set}_start_method
Richard Oudkerk
report at bugs.python.org
Thu Sep 12 17:10:24 CEST 2013
Richard Oudkerk added the comment:
There are lots of things that behave differently depending on the currently set start method: Lock(), Semaphore(), Queue(), Value(), ... It is not just when creating a Process or Pool that you need to know the start method.
Passing a context or start_method argument to all of these constructors would be very awkward, which is why I think it is better to treat the context as an object with methods Process(), Pool(), Lock(), Semaphore(), etc.
Unfortunately, I do not have time to work on this just now...
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18999>
_______________________________________
More information about the Python-bugs-list
mailing list