Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-12-08 06:10:17 +00:00
Code Issues Projects Releases Packages Wiki Activity

[3.14] Doc/library/os.rst: Remove spurious parenthesis (GH-139205) (#139217)

Browse source 
`Doc/library/os.rst`: Remove spurious parenthesis (GH-139205)
(cherry picked from commit 9c3d09b984)

Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com>
This commit is contained in:
Miss Islington (bot) 2025-09-21 21:56:06 +02:00 • committed by GitHub
parent 665a3495bf
commit ccdc0c9992
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Doc/library/os.rst
View file

@ -2009,8 +2009,8 @@ features:
must be a string specifying a file path. However, some functions now must be a string specifying a file path. However, some functions now
alternatively accept an open file descriptor for their *path* argument. alternatively accept an open file descriptor for their *path* argument.
The function will then operate on the file referred to by the descriptor. The function will then operate on the file referred to by the descriptor.
(For POSIX systems, Python will call the variant of the function prefixed For POSIX systems, Python will call the variant of the function prefixed
with ``f`` (e.g. call ``fchdir`` instead of ``chdir``).) with ``f`` (e.g. call ``fchdir`` instead of ``chdir``).
You can check whether or not *path* can be specified as a file descriptor You can check whether or not *path* can be specified as a file descriptor
for a particular function on your platform using :data:`os.supports_fd`. for a particular function on your platform using :data:`os.supports_fd`.
@ -2025,7 +2025,7 @@ features:
* **paths relative to directory descriptors:** If *dir_fd* is not ``None``, it * **paths relative to directory descriptors:** If *dir_fd* is not ``None``, it
should be a file descriptor referring to a directory, and the path to operate should be a file descriptor referring to a directory, and the path to operate
on should be relative; path will then be relative to that directory. If the on should be relative; path will then be relative to that directory. If the
path is absolute, *dir_fd* is ignored. (For POSIX systems, Python will call path is absolute, *dir_fd* is ignored. For POSIX systems, Python will call
the variant of the function with an ``at`` suffix and possibly prefixed with the variant of the function with an ``at`` suffix and possibly prefixed with
``f`` (e.g. call ``faccessat`` instead of ``access``). ``f`` (e.g. call ``faccessat`` instead of ``access``).
@ -2038,8 +2038,8 @@ features:
* **not following symlinks:** If *follow_symlinks* is * **not following symlinks:** If *follow_symlinks* is
``False``, and the last element of the path to operate on is a symbolic link, ``False``, and the last element of the path to operate on is a symbolic link,
the function will operate on the symbolic link itself rather than the file the function will operate on the symbolic link itself rather than the file
pointed to by the link. (For POSIX systems, Python will call the ``l...`` pointed to by the link. For POSIX systems, Python will call the ``l...``
variant of the function.) variant of the function.
You can check whether or not *follow_symlinks* is supported for a particular You can check whether or not *follow_symlinks* is supported for a particular
function on your platform using :data:`os.supports_follow_symlinks`. function on your platform using :data:`os.supports_follow_symlinks`.