Skip to content

gh-130209: Retry path-based os functions on EINTR #160544

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

Open
larryhastings wants to merge 2 commits into
base: main
Choose a base branch
from
Open

gh-130209: Retry path-based os functions on EINTR #160544

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f867952
Extends PEP 475 retry behavior to more os functions that take a path.
larryhastings Oct 23, 2026
a971275
Merge branch 'main' into pep475plus
larryhastings Oct 24, 2026
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
10 changes: 10 additions & 0 deletions Misc/NEWS.d/next/Library/2026-10-23-16-06-39.gh-issue-130209.q_hzoM.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
Added retry loops to functions in :mod:`os` that interact with the
filesystem, such as :func:`~os.stat`, :func:`~os.rename`, :func:`~os.utime`,
:func:`~os.unlink`, :func:`~os.listdir` and :func:`~os.scandir`. On POSIX,
if a system call fails and ``errno`` is set to ``EINTR``, it means a signal
was delivered to the process and interrupted the call; the recommended
course of action is to handle the signal and retry. :pep:`475` added retry
loops for a number of functions in the :mod:`os` module, but skipped most of
the functions that take a *path* argument, because those don't normally
result in ``EINTR``. However, they *can* (and do!) on network filesystems
(e.g. NFS) and userspace filesystems (e.g. FUSE).
Loading
Loading