https://github.com/python/cpython/commit/df8ae2828689d929ce05a92188cca02387e66005 commit: df8ae2828689d929ce05a92188cca02387e66005 branch: 3.13 author: Miss Islington (bot) <[email protected]> committer: ZeroIntensity <[email protected]> date: 2025-09-21T19:05:42Z summary:
[3.13] `Doc/library/os.rst`: Remove spurious parenthesis (GH-139205) (GH-139218) `Doc/library/os.rst`: Remove spurious parenthesis (GH-139205) (cherry picked from commit 9c3d09b984374292d1d8552f53c98f445f8556dd) Co-authored-by: Stan Ulbrych <[email protected]> files: M Doc/library/os.rst diff --git a/Doc/library/os.rst b/Doc/library/os.rst index a03270224a4522..946db4220b6b9e 100644 --- a/Doc/library/os.rst +++ b/Doc/library/os.rst @@ -1937,8 +1937,8 @@ features: must be a string specifying a file path. However, some functions now alternatively accept an open file descriptor for their *path* argument. 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 - with ``f`` (e.g. call ``fchdir`` instead of ``chdir``).) + For POSIX systems, Python will call the variant of the function prefixed + with ``f`` (e.g. call ``fchdir`` instead of ``chdir``). 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`. @@ -1953,7 +1953,7 @@ features: * **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 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 ``f`` (e.g. call ``faccessat`` instead of ``access``). @@ -1966,8 +1966,8 @@ features: * **not following symlinks:** If *follow_symlinks* is ``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 - pointed to by the link. (For POSIX systems, Python will call the ``l...`` - variant of the function.) + pointed to by the link. For POSIX systems, Python will call the ``l...`` + variant of the function. You can check whether or not *follow_symlinks* is supported for a particular function on your platform using :data:`os.supports_follow_symlinks`. _______________________________________________ Python-checkins mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/python-checkins.python.org Member address: [email protected]
