Skip to content

fcntl.lockf() is more powerful than written #6750

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 13, 2019
Merged

fcntl.lockf() is more powerful than written #6750

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
33c0c41
fcntl.lockf() is better than what is in the documentation
lebigot May 10, 2018
20f1198
Used the standard function/method ReST mark
lebigot May 10, 2018
91aa8a6
Use the same wording as the other one.
JulienPalard Sep 13, 2019
039321a
rewrap
JulienPalard Sep 13, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Doc/library/fcntl.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,8 @@ The module defines the following functions:
.. function:: lockf(fd, cmd, len=0, start=0, whence=0)

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:

* :const:`LOCK_UN` -- unlock
Expand Down Expand Up @@ -167,4 +168,3 @@ using the :func:`flock` call may be better.
present in the :mod:`os` module (on BSD only), the :func:`os.open`
function provides an alternative to the :func:`lockf` and :func:`flock`
functions.