➜

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 christian.heimes
Recipients alexey-smirnov, amaury.forgeotdarc, christian.heimes, neologix, sbt, vstinner
Date 2013-01-03.16:25:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357230329.27.0.988994999232.issue16850@psf.upfronthosting.co.za>
In-reply-to
Content 
Do you mean #12105? I didn't know about the ticket before.

How about two options, like 'e' for guaranteed atomic CLOEXEC and 'E' for CLOEXEC with or without atomic ops? It's not much additional work and lowers the burden on the user.

It's going to be hard to get a list of platforms and versions where O_CLOEXEC is supported. We should go for a white list approach and only enable it on platforms that are either documented to support it or have been tested.
History
Date User Action Args
2013-01-03 16:25:29christian.heimessetrecipients: + christian.heimes, amaury.forgeotdarc, vstinner, neologix, sbt, alexey-smirnov
2013-01-03 16:25:29christian.heimessetmessageid: <1357230329.27.0.988994999232.issue16850@psf.upfronthosting.co.za>
2013-01-03 16:25:29christian.heimeslinkissue16850 messages
2013-01-03 16:25:29christian.heimescreate