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 ncoghlan
Recipients Jim.Jewett, The Compiler, ezio.melotti, martin.panter, mbussonn, ncoghlan, njs, rbcollins, serhiy.storchaka, takluyver, terry.reedy
Date 2015-08-25.06:03:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As Robert suggests, I think it's OK to issue the deprecation warnings for code run via "python <" or "cat | python". Reverting to the current behaviour if folks actually want that would just be a matter of passing the file in directly, rather than piping it via stdin: "python".

That eliminates any need to care about whether the input is a tty or not, and we can just focus on the code paths. If you grep the CPython code base for "ps1" you're likely to find most of the relevant places ("sys.ps1" hold the interactive prompt, while "sys.ps2" holds the continuation prompt)
Date User Action Args
2015-08-25 06:03:04ncoghlansetrecipients: + ncoghlan, terry.reedy, rbcollins, ezio.melotti, njs, takluyver, martin.panter, Jim.Jewett, serhiy.storchaka, The Compiler, mbussonn
2015-08-25 06:03:04ncoghlansetmessageid: <>
2015-08-25 06:03:04ncoghlanlinkissue24294 messages
2015-08-25 06:03:03ncoghlancreate