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-05-17.07:48:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My point is that in five years' time some existing well-tested sysadmin-like program will be run with Python 3.4 for the first time, and suddenly whole systems will break.  I don't want to sound negative but this is the worst behavior ever (with the possible exception of programs that do bad things beyond your own system, like viruses).  Please at least crash with an exception instead: add one easy check to py_compile.compile() and complain if cfile points to an existing non-regular file.
Date User Action Args
2013-05-17 07:48:29arigosetrecipients: + arigo, barry, brett.cannon, ncoghlan, pitrou, Arfrever, python-dev, eric.snow
2013-05-17 07:48:29arigosetmessageid: <>
2013-05-17 07:48:29arigolinkissue17222 messages
2013-05-17 07:48:28arigocreate