[issue46367] multiprocessing's "spawn" doesn't actually use spawn

STINNER Victor added the comment: > It appears the `multiprocessing`'s "spawn" mode doesn't actually use POSIX > spawn, but instead uses fork+exec[1]. The documentation doesn't pretend to use posix_spawn(). It only says: "starts a fresh python interpreter process".

[issue46367] multiprocessing's "spawn" doesn't actually use spawn

Change by Irit Katriel : -- nosy: +vstinner versions: -Python 3.7, Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue46367] multiprocessing's "spawn" doesn't actually use spawn

New submission from jakirkham : Reporting an issue recently encountered by a colleague. It appears the `multiprocessing`'s "spawn" mode doesn't actually use POSIX spawn, but instead uses fork+exec[1]. While this is certainly a useful feature in its own right, this not quite one would expect