Doc: fcntl.lockf() is more powerful than written (GH-6750)

This commit is contained in:
Eric O. LEBIGOT (EOL) 2019-09-13 19:32:28 +02:00 committed by Stéphane Wirtel
parent 0bc17ea2f5
commit 77cd0ceab2
1 changed files with 2 additions and 2 deletions

View File

@ -124,7 +124,8 @@ The module defines the following functions:
.. function:: lockf(fd, cmd, len=0, start=0, whence=0) .. function:: lockf(fd, cmd, len=0, start=0, whence=0)
This is essentially a wrapper around the :func:`~fcntl.fcntl` locking calls. This is essentially a wrapper around the :func:`~fcntl.fcntl` locking calls.
*fd* is the file descriptor of the file to lock or unlock, and *cmd* *fd* is the file descriptor (file objects providing a :meth:`~io.IOBase.fileno`
method are accepted as well) of the file to lock or unlock, and *cmd*
is one of the following values: is one of the following values:
* :const:`LOCK_UN` -- unlock * :const:`LOCK_UN` -- unlock
@ -175,4 +176,3 @@ using the :func:`flock` call may be better.
present in the :mod:`os` module (on BSD only), the :func:`os.open` present in the :mod:`os` module (on BSD only), the :func:`os.open`
function provides an alternative to the :func:`lockf` and :func:`flock` function provides an alternative to the :func:`lockf` and :func:`flock`
functions. functions.