This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients Arfrever, brett.cannon, eric.snow, ncoghlan, pitrou
Date 2013-02-19.14:36:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So that all happens because importlib does an atomic write of the file which uses os.replace(): .

Unless there is some way that I can't think of to have the atomic write still exist but not change the type of file it replaces I am still not willing to revert my change just for this use case. There should be a single implementation of bytecode file generation and py_compile (along with compileall) should be nothing more than convenience modules for forcing the generation of those files under the same semantics as if they were done as a side-effect of importing some source code.
Date User Action Args
2013-02-19 14:36:25brett.cannonsetrecipients: + brett.cannon, ncoghlan, pitrou, Arfrever, eric.snow
2013-02-19 14:36:25brett.cannonsetmessageid: <>
2013-02-19 14:36:25brett.cannonlinkissue17222 messages
2013-02-19 14:36:24brett.cannoncreate