[Python-checkins] peps: PEP 433: fix typo, sys.setdefaultcloexec() has one mandatory parameter

Wed Jan 30 09:42:23 CET 2013

http://hg.python.org/peps/rev/c8017823a4dc
changeset: 4700:c8017823a4dc
user: Victor Stinner <victor.stinner at gmail.com>
date: Wed Jan 30 09:40:36 2013 +0100
summary:
 PEP 433: fix typo, sys.setdefaultcloexec() has one mandatory parameter
files:
 pep-0433.txt | 6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/pep-0433.txt b/pep-0433.txt
--- a/pep-0433.txt
+++ b/pep-0433.txt
@@ -20,7 +20,7 @@
 * ``os.get_cloexec(fd)``
 * ``os.set_cloexec(fd, cloexec=True)``
 * ``sys.getdefaultcloexec()``
- * ``sys.setdefaultcloexec(cloexec=True)``
+ * ``sys.setdefaultcloexec(cloexec)``
 
 
 Rationale
@@ -39,7 +39,7 @@
 the *bInheritHandles* parameter set to ``TRUE`` (when
 ``subprocess.Popen`` is created with ``close_fds=False`` for example).
 Windows does now have "close-on-exec" flag but an inherance flag which
-is just the opposite value. For example, setting close-on-exec flag set
+is just the opposite value. For example, setting close-on-exec flag
 means clearing the ``HANDLE_FLAG_INHERIT`` flag of an handle.
 
 
@@ -192,7 +192,7 @@
 platforms.
 * ``sys.getdefaultcloexec() -> bool``: get the current default value
 of the *cloexec* parameter
- * ``sys.setdefaultcloexec(cloexec: bool=True)``: set the default value
+ * ``sys.setdefaultcloexec(cloexec: bool)``: set the default value
 of the *cloexec* parameter
 
 Add a new optional *cloexec* parameter to:
-- 
Repository URL: http://hg.python.org/peps
