PEP 433: fix typo, sys.setdefaultcloexec() has one mandatory parameter

This commit is contained in:
Victor Stinner 2013-01-30 09:40:36 +01:00
parent 60f6b766a4
commit 8794e08fd7
1 changed files with 3 additions and 3 deletions

View File

@ -20,7 +20,7 @@ parameter, and add four new functions:
* ``os.get_cloexec(fd)``
* ``os.set_cloexec(fd, cloexec=True)``
* ``sys.getdefaultcloexec()``
* ``sys.setdefaultcloexec(cloexec=True)``
* ``sys.setdefaultcloexec(cloexec)``
Rationale
@ -39,7 +39,7 @@ close-on-exec flag is cleared and if ``CreateProcess()`` is called with
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 @@ Add new functions:
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: