New submission from Martin Panter: I noticed that this test leaves processes running in the background for a moment after the parent Python process exits. They disappear pretty quickly, but even so, it seems like a bad design. However I am not familiar with the multiprocessing module, so maybe this is unavoidable.
$ ps PID TTY TIME CMD 597 pts/2 00:00:01 bash 13423 pts/2 00:00:00 ps $ python3.5 -m test test_multiprocessing_spawn; ps [1/1] test_multiprocessing_spawn 1 test OK. PID TTY TIME CMD 597 pts/2 00:00:01 bash 13429 pts/2 00:00:00 python3.5 13475 pts/2 00:00:00 python3.5 15066 pts/2 00:00:00 ps ---------- components: Tests messages: 263442 nosy: martin.panter priority: normal severity: normal status: open title: test_multiprocessing_spawn leaves processes running in background type: behavior versions: Python 3.5, Python 3.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26762> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
