When trying to write new bytecode, importlib was not catching the IOError

thrown if the file happened to be read-only to keep the failure silent.

Fixes issue #7187. Thanks, Dave Malcolm for the report and analysis of the
problem.
This commit is contained in:
Brett Cannon 2009-11-07 23:55:05 +00:00
parent 1b184d547f
commit e52c919d67
4 changed files with 32 additions and 2 deletions

View file

@ -123,6 +123,9 @@ C-API
Library
-------
- Issue #7187: Importlib would not silence the IOError raised when trying to
write new bytecode when it was made read-only.
- Issue #7264: Fix a possible deadlock when deallocating thread-local objects
which are part of a reference cycle.