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 njs
Recipients Jim.Jewett, The Compiler, ezio.melotti, martin.panter, mbussonn, ncoghlan, njs, serhiy.storchaka, takluyver, terry.reedy
Date 2015-08-20.17:31:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If pty is going to work at all then it should work regardless of whether the tests themselves are being run under a tty, yes.

I personally would not want to merge a test based on making isatty lie, because the point of tests is to increase confidence that things work, and that test sounds more complicated and error prone than the original code being tested. I'm not a cpython committer though...

I am more concerned that isatty might actually just not work on windows, since it is actually strictly speaking true that you never have a "try" on Windows, even if you might have a gui console window open. It would be a good idea to check this quickly...

The other option would be to just remove the isatty check from the patch entirely -- it wasn't something that had strong consensus in the first place.
Date User Action Args
2015-08-20 17:31:38njssetrecipients: + njs, terry.reedy, ncoghlan, ezio.melotti, takluyver, martin.panter, Jim.Jewett, serhiy.storchaka, The Compiler, mbussonn
2015-08-20 17:31:38njssetmessageid: <>
2015-08-20 17:31:38njslinkissue24294 messages
2015-08-20 17:31:38njscreate