[New-bugs-announce] [issue9663] importlib should exclusively open bytecode files

Brett Cannon report at bugs.python.org
Mon Aug 23 00:24:13 CEST 2010


New submission from Brett Cannon <brett at python.org>:

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 flat-out import failure and not simply glossed over.

Plus if I don't do this now I will just end up getting a bug report that test_multiprocessing is randomly failing on the buildbots because of this issue since that "precious" little test seems to love to ferret out concurrency issues in importlib.

----------
assignee: brett.cannon
components: Library (Lib)
messages: 114714
nosy: brett.cannon
priority: normal
severity: normal
stage: unit test needed
status: open
title: importlib should exclusively open bytecode files
type: behavior
versions: Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9663>
_______________________________________


More information about the New-bugs-announce mailing list