RetroSearch Browse

Tue Jan 29 12:46:09 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-January/123762.html

On Tue, Jan 29, 2013 at 4:13 PM, Charles-François Natali
<cf.natali at gmail.com> wrote:
> So I'm definitely -1 against any form of tunable value (be it a
> sys.setdefaultcloexec(), an environment variable or command-line
> flag), and still against changing the default value.

I now think the conservative option is to initially implement the
design in 3.4 without an option to change the global default. The
"cloexec=True/False" model at least *supports* a tunable default, as
well as eventually *changing* the default if we choose to do so, but I
don't think there's any hurry to proceed to those steps.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-January/123762.html below:

Choose the default value of the new cloexec parameter