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 neologix
Recipients gregory.p.smith, jyasskin, loewis, nadeem.vawda, neologix, pitrou, rosslagerwall, s7v7nislands, vstinner
Date 2011-03-27.11:00:58
SpamBayes Score 2.2828437e-05
Marked as misclassified No
Message-id <1301223659.43.0.22760850493.issue8052@psf.upfronthosting.co.za>
In-reply-to
Content
If you're suggesting to set FDs CLOEXEC by default, I think it's neither possible nor reasonable:
- you have to take into account not only files, but also pipes, sockets, etc
- there's no portable way to e.g. open a file and set it CLOEXEC atomically
- first and foremost, it' going to break a lot of existing code, for example, pipe + fork, accept + fork, etc
As for the dedicated syscalls, there's already been some discussion about closefrom and friends, but Gregory did some research and it looked like those are not async-safe - which, if it's really the case, renders those calls mostly useless.
History
Date User Action Args
2011-03-27 11:00:59neologixsetrecipients: + neologix, loewis, gregory.p.smith, pitrou, vstinner, jyasskin, nadeem.vawda, s7v7nislands, rosslagerwall
2011-03-27 11:00:59neologixsetmessageid: <1301223659.43.0.22760850493.issue8052@psf.upfronthosting.co.za>
2011-03-27 11:00:58neologixlinkissue8052 messages
2011-03-27 11:00:58neologixcreate