[issue16946] subprocess: _close_open_fd_range_safe() does not set close-on-exec flag on Linux 2.6.23 if O_CLOEXEC is defined

2013-08-27 Thread STINNER Victor
STINNER Victor added the comment: This issue has been fixed in the implementation of the PEP 446 (issue #18571). -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16946

[issue16946] subprocess: _close_open_fd_range_safe() does not set close-on-exec flag on Linux 2.6.23 if O_CLOEXEC is defined

2013-01-29 Thread STINNER Victor
STINNER Victor added the comment: This issue is fixed in my implementation of the PEP 433: see #17036. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16946 ___

[issue16946] subprocess: _close_open_fd_range_safe() does not set close-on-exec flag on Linux 2.6.23 if O_CLOEXEC is defined

2013-01-12 Thread STINNER Victor
New submission from STINNER Victor: The following extract of _close_open_fd_range_safe() is not correct: #ifdef O_CLOEXEC fd_dir_fd = open(FD_DIR, O_RDONLY | O_CLOEXEC, 0); #else fd_dir_fd = open(FD_DIR, O_RDONLY, 0); #ifdef FD_CLOEXEC { int old = fcntl(fd_dir_fd, F_GETFD);

[issue16946] subprocess: _close_open_fd_range_safe() does not set close-on-exec flag on Linux 2.6.23 if O_CLOEXEC is defined

2013-01-12 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +gps ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16946 ___ ___ Python-bugs-list

[issue16946] subprocess: _close_open_fd_range_safe() does not set close-on-exec flag on Linux 2.6.23 if O_CLOEXEC is defined

2013-01-12 Thread Gregory P. Smith
Changes by Gregory P. Smith g...@krypto.org: -- assignee: - gregory.p.smith nosy: +gregory.p.smith -gps ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16946 ___