This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ita1024
Recipients ita1024, martin.panter, python-dev, vstinner
Date 2017-01-06.22:54:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483743285.2.0.241375657716.issue29174@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-01-06 22:54:45ita1024setrecipients: + ita1024, vstinner, python-dev, martin.panter
2017-01-06 22:54:45ita1024setmessageid: <1483743285.2.0.241375657716.issue29174@psf.upfronthosting.co.za>
2017-01-06 22:54:45ita1024linkissue29174 messages
2017-01-06 22:54:45ita1024create