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 steve.dower
Recipients efiop, eryksun, gregory.p.smith, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-06-26.01:56:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561514181.64.0.298891015968.issue37380@roundup.psfhosted.org>
In-reply-to
Content
The handle can deliberately live beyond the process, but it does not have to. If it is closed early then the kernel object will be freed when no handles remain, which will be at process exit.

So it's a classic __exit__/__del__ case, where both are needed if you want deterministic resource disposal. But it is in no way tied to the life of the child process, so waiting first is optional.
History
Date User Action Args
2019-06-26 01:56:21steve.dowersetrecipients: + steve.dower, gregory.p.smith, paul.moore, vstinner, tim.golden, zach.ware, eryksun, efiop
2019-06-26 01:56:21steve.dowersetmessageid: <1561514181.64.0.298891015968.issue37380@roundup.psfhosted.org>
2019-06-26 01:56:21steve.dowerlinkissue37380 messages
2019-06-26 01:56:21steve.dowercreate