➜

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 pitrou
Recipients Arfrever, brett.cannon, eric.snow, ncoghlan, pitrou
Date 2013-02-19.17:05:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1361293526.65.0.320614827817.issue17222@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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

How about using the `mode` to write_atomic?
(which, incidentally, is already used to mirror the .py file's permissions in SourceFileLoader._cache_bytecode)
History
Date User Action Args
2013-02-19 17:05:26pitrousetrecipients: + pitrou, brett.cannon, ncoghlan, Arfrever, eric.snow
2013-02-19 17:05:26pitrousetmessageid: <1361293526.65.0.320614827817.issue17222@psf.upfronthosting.co.za>
2013-02-19 17:05:26pitroulinkissue17222 messages
2013-02-19 17:05:26pitroucreate