Message263442
| Author |
martin.panter |
| Recipients |
martin.panter |
| Date |
2016年04月15日.04:04:24 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1460693065.24.0.946570360611.issue26762@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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 |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年04月15日 04:04:25 | martin.panter | set | recipients:
+ martin.panter |
| 2016年04月15日 04:04:25 | martin.panter | set | messageid: <1460693065.24.0.946570360611.issue26762@psf.upfronthosting.co.za> |
| 2016年04月15日 04:04:25 | martin.panter | link | issue26762 messages |
| 2016年04月15日 04:04:24 | martin.panter | create |
|