This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zbysz
Recipients zbysz
Date 2020-07-02.09:13:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
[Originally reported as]

$ touch ~/foo
touch: cannot touch '/home/fedora/foo': Read-only file system
$ python
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.
>>> ^D
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/usr/lib64/python3.9/", line 462, in write_history
OSError: [Errno 30] Read-only file system

Looking at /usr/lib64/python3.9/, 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 b2499669ef2e6dc9a2cdb49b4dc498e078167e26.

Version-Release number of selected component (if applicable):
Date User Action Args
2020-07-02 09:13:51zbyszsetrecipients: + zbysz
2020-07-02 09:13:51zbyszsetmessageid: <>
2020-07-02 09:13:51zbyszlinkissue41193 messages
2020-07-02 09:13:51zbyszcreate