Message284867
The point #3 was referring to the new requirement for an atexit handler in order to not only kill the processes but to also wait for them at interpreter shutdown. The sub-processes (and associated resources) in the example are definitely freed as the parent process is terminating.
The recommended handler is not even always desirable (spawning daemon processes, key agents), it increases the code verbosity, impacts performance, and can even cause problems as child processes cannot always be waited on reliably (python 2 but also child -D state and platform-specific restrictions).
I suggest to disable such warnings during interpreter shutdown. |
|
Date |
User |
Action |
Args |
2017-01-06 22:54:45 | ita1024 | set | recipients:
+ ita1024, vstinner, python-dev, martin.panter |
2017-01-06 22:54:45 | ita1024 | set | messageid: <1483743285.2.0.241375657716.issue29174@psf.upfronthosting.co.za> |
2017-01-06 22:54:45 | ita1024 | link | issue29174 messages |
2017-01-06 22:54:45 | ita1024 | create | |
|