On Tue, Jan 29, 2013 at 4:13 PM, Charles-François Natali <cf.nat...@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 | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
