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 arigo
Recipients Arfrever, arigo, barry, brett.cannon, eric.snow, ncoghlan, pitrou, python-dev
Date 2013-06-05.13:45:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Brett: I don't really have a constructive opinion on this matter.  I could suggest putting a bit more logic in py_compile.compile(cfile=...) to revert to the old behavior if we specify an already-existing target, in order to fix the other reported issue that custom permissions set on the target file are lost.  But I would understand if you decide that this is not compatible with the gains of atomic file creations.  I only have a problem with replacing block devices with regular files.  I don't have a particular opinion if the target file is a symlink (as long, of course, as it doesn't lead to whatever it points to being replaced, but it shouldn't).
Date User Action Args
2013-06-05 13:45:34arigosetrecipients: + arigo, barry, brett.cannon, ncoghlan, pitrou, Arfrever, python-dev, eric.snow
2013-06-05 13:45:34arigosetmessageid: <>
2013-06-05 13:45:34arigolinkissue17222 messages
2013-06-05 13:45:33arigocreate