sys.stdin and two CTRL-Ds

[cmdrrickhunter@yaho.com]

I may be wrong, but I've never heard of Windows being fully posix
compliant.  I guarentee you that they dont support pthreads.

It is possible that by "posix compliant" the marketting execs mean
"supports all posix commands which dont interfere with our way of doing
things"

Windows version of python always uses \r\n for line ends (which are
then combined into a single \n character when read).  This bears strong
resemblance to the carriage return line feed combination required by
typerwriters before the computer era.  Wordpad will read Unix line ends
(\n) if it has to, notepad wont even try.  Mac used to use \r for line
ends, just to be the odd ball.  I think they may have stopped that with
OSX. Any mac user want to cover this one?

Whats especially frustrating is the cygwin version of python.  If you
configure things wrong with the cygwin line ends, you can have python
swear its outputing \n while its really coughing out \r\n's


Lawrence D'Oliveiro wrote:
> Why should that matter? I thought Windows (the NT line) was
> POSIX-compliant.