[issue9663] importlib should exclusively open bytecode files

Brett Cannon added the comment: Fixed by Issue13146. -- resolution: -> out of date stage: test needed -> status: open -> closed superseder: -> Writing a pyc file is not atomic ___ Python tracker

[issue9663] importlib should exclusively open bytecode files

Jesse Noller added the comment: Nice. -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9663] importlib should exclusively open bytecode files

New submission from Brett Cannon : Importlib does not use any OS-level protections to gain exclusivity when opening a file like import.c does through open_exclusive. It probably should, though, when writing bytecode else one might end up with corrupt code. That's bad as bad marshal data is a f