[issue19946] Have multiprocessing raise ImportError when spawning a process that can't find the "main" module
Antoine Pitrou
report at bugs.python.org
Fri Dec 13 20:26:27 CET 2013
Antoine Pitrou added the comment:
Let's reopen, shall we? If not for 3.4, at least for 3.5.
It's likely that multiprocessing needs a __main__ simply because it needs a way to replicate the parent process' state in the child (for example, the set of imported modules, the logging configuration, etc.). Perhaps Richard can elaborate.
But, AFAIU, the __main__ could be imported as a script rather than a "proper" module from sys.path.
----------
assignee: brett.cannon ->
status: closed -> open
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue19946>
_______________________________________
More information about the Python-bugs-list
mailing list