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, arigo, barry, brett.cannon, eric.snow, ncoghlan, pitrou, python-dev
Date 2013-05-17.07:22:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, the switch to renaming can change behaviour in some corner cases (I say "corner cases" because the expected situation is to have your pyc files be regular files, not symlinks or character devices). Python is certainly not the only application where you can bust /dev/null by specifying it as target location.

Mutating a file in place is a source of unpredictable issues with concurrent access of the file being written to, which is why it was changed to renaming. I think the class of issues which was solved (presumably) is much more important than the use case of compiling to /dev/null.

As for symlinks, I'd naively expect breaking symlinks to be a feature, but YMMV.
Date User Action Args
2013-05-17 07:22:41pitrousetrecipients: + pitrou, barry, brett.cannon, arigo, ncoghlan, Arfrever, python-dev, eric.snow
2013-05-17 07:22:41pitrousetmessageid: <>
2013-05-17 07:22:41pitroulinkissue17222 messages
2013-05-17 07:22:41pitroucreate