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 eryksun
Recipients Kevin, astanton1978, erik.bray, eryksun, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2019-04-12.15:35:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555083308.69.0.631949351907.issue32451@roundup.psfhosted.org>
In-reply-to
Content
> This is assuming that in all these cases people are installing Python 
> for Windows and trying to use it from a non-Windows shell (both WSL 
> and Cygwin have their own "native" Python builds that presumably 
> work).

It should work from Cygwin and MSYS2 since they support DOS paths in $PATH. I don't have Cygwin installed, but I tried MSYS2 bash and Git bash, and it worked fine, even with CRLF line endings. Apparently only Cygwin bash has a problem with CRLF line endings. 

The issue with using Windows Python in this case is that the terminals for these environments emulate Unix PTYs with named pipes (e.g. "msys-0123456789abcdef-pty0-from-master" for stdin and "msys-0123456789abcdef-pty0-to-master" for stdout and stderr). Thus isatty() is false, and interactive mode has to be forced with the `-i` command-line option.
History
Date User Action Args
2019-04-12 15:35:08eryksunsetrecipients: + eryksun, paul.moore, tim.golden, r.david.murray, erik.bray, zach.ware, steve.dower, Kevin, astanton1978
2019-04-12 15:35:08eryksunsetmessageid: <1555083308.69.0.631949351907.issue32451@roundup.psfhosted.org>
2019-04-12 15:35:08eryksunlinkissue32451 messages
2019-04-12 15:35:08eryksuncreate