➜

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 gvanrossum
Recipients christian.heimes, gvanrossum, martius, neologix, vstinner, yselivanov
Date 2015-05-26.20:30:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432672226.19.0.474389697549.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't actually know if the 5th option is possible. My strong requirement is that no matter what the child process does, the parent should still be able to continue using the loop. IMO it's better to leak a FD in the child than to close a resource owned by the parent. Within those constraints I'm okay with various solutions.
History
Date User Action Args
2015-05-26 20:30:26gvanrossumsetrecipients: + gvanrossum, vstinner, christian.heimes, neologix, yselivanov, martius
2015-05-26 20:30:26gvanrossumsetmessageid: <1432672226.19.0.474389697549.issue21998@psf.upfronthosting.co.za>
2015-05-26 20:30:26gvanrossumlinkissue21998 messages
2015-05-26 20:30:26gvanrossumcreate