[Originally reported as https://bugzilla.redhat.com/show_bug.cgi?id=1852941.]
$ touch ~/foo
touch: cannot touch '/home/fedora/foo': Read-only file system
Python 3.9.0b3 (default, Jun 10 2020, 00:00:00)
[GCC 10.1.1 20200507 (Red Hat 10.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib64/python3.9/site.py", line 462, in write_history
OSError: [Errno 30] Read-only file system
Looking at /usr/lib64/python3.9/site.py, it already silently skips
PermissionError. If a user is running with the file system in ro mode,
they almost certainly are aware of the fact, since this is done either
on purpose or as a result of disk corruption, and the traceback from
python is not useful. Suppression of PermissionError was added in b249966.
Version-Release number of selected component (if applicable):
Well, two errors were already ignored (bpo-19891). I just made the "except" more generic. I don't think that we can do anything more useless than ignoring the error if the filesystem is read-only. I don't think that a warning would be useful.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
The text was updated successfully, but these errors were encountered: