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 Emil.Styrke
Recipients Emil.Styrke, amaury.forgeotdarc, brian.curtin, eckhardt, eryksun, ggenellina, javen72, terry.reedy
Date 2015-03-27.06:01:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1427436102.08.0.942340919528.issue4944@psf.upfronthosting.co.za>
In-reply-to
Content
eryksun, thank you for the explanation, the penny finally dropped for me.  It's the *other* child processes that keep the file open, not the parent.  Actually this bug started hitting me after I *stopped* doing exactly what you suggest (fdopen on the temp file), and instead started using file names generated by my program (opened with regular "open") and now I see why that is.  If I use os.fdopen with the O_NOINHERIT flag, it works as expected.
History
Date User Action Args
2015-03-27 06:01:42Emil.Styrkesetrecipients: + Emil.Styrke, terry.reedy, amaury.forgeotdarc, ggenellina, eckhardt, javen72, brian.curtin, eryksun
2015-03-27 06:01:42Emil.Styrkesetmessageid: <1427436102.08.0.942340919528.issue4944@psf.upfronthosting.co.za>
2015-03-27 06:01:42Emil.Styrkelinkissue4944 messages
2015-03-27 06:01:41Emil.Styrkecreate