[issue13392] Writing a pyc file is not atomic under Windows

Roundup Robot added the comment: New changeset 12940d9f8031 by Antoine Pitrou in branch 'default': Fix regression under Windows following b75b41237380 (from issue #13392) http://hg.python.org/cpython/rev/12940d9f8031 -- ___ Python tracker

[issue13392] Writing a pyc file is not atomic under Windows

Antoine Pitrou added the comment: Ok, done. Let's see if that fixes the sporadic failures on the buildbots. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue13392] Writing a pyc file is not atomic under Windows

Roundup Robot added the comment: New changeset b75b41237380 by Antoine Pitrou in branch 'default': Issue #13392: Writing a pyc file should now be atomic under Windows as well. http://hg.python.org/cpython/rev/b75b41237380 -- ___ Python tracker

[issue13392] Writing a pyc file is not atomic under Windows

Brett Cannon added the comment: I say go with the deletion for importlib. If the failure is a sign of success, then just go with it and not worry about the failure. __pycache__ guarantees that we are not losing out by clobbering some other Python version's pyc file. -- __

[issue13392] Writing a pyc file is not atomic under Windows

New submission from Antoine Pitrou : #13146 solved the issue of writing pyc files under POSIX. Under Windows, the problem still exists, as the following buildbot failure shows: [317/360] test_multiprocessing Traceback (most recent call last): File "", line 1, in File "D:\cygwin\home\db3l\