[issue16139] Python 3.3 fails when starting from read-only FS

Charles-François Natali added the comment: > This is more or less a duplicate of #15833 Indeed, closing as duplicate. -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> most failures to write byte-compiled file no longer suppressed type: cr

[issue16139] Python 3.3 fails when starting from read-only FS

Richard Oudkerk added the comment: This is more or less a duplicate of #15833 (although the errno mentioned there is EIO instead of the more sensible EROFS). -- nosy: +sbt ___ Python tracker __

[issue16139] Python 3.3 fails when starting from read-only FS

Charles-François Natali added the comment: > Hmm... I guess maybe we should trap all OSErrors after all (and print the > error when in verbose mode). Yes. -- ___ Python tracker ___

[issue16139] Python 3.3 fails when starting from read-only FS

Antoine Pitrou added the comment: Hmm... I guess maybe we should trap all OSErrors after all (and print the error when in verbose mode). -- nosy: +neologix, pitrou ___ Python tracker __

[issue16139] Python 3.3 fails when starting from read-only FS

STINNER Victor added the comment: Python 3.2 logs an error to stderr (if Python is started in verbose mode) if the directory and/or the pyc file cannot be created, and continue. #ifdef MS_WINDOWS if (_mkdir(cpathname) < 0 && errno != EEXIST) { #else if (mkdir(cpathname, dirmode) < 0 &&

[issue16139] Python 3.3 fails when starting from read-only FS

Changes by R. David Murray : -- nosy: +brett.cannon type: behavior -> crash versions: +Python 3.4 ___ Python tracker ___ ___ Python-bu

[issue16139] Python 3.3 fails when starting from read-only FS

New submission from Andrew Gallagher: This occurs when python is installed on a read-only mount AND all the .pyc files are out-of-date. Therefore, when python starts and attempts to write a new .pyc file, _write_atomic in "Lib/importlib/_bootstrap.py" throws an OSError with an errno of EROFS,