It seems like os.isatty(0) works on Windows too. Documentation says Unix only:

  http://docs.python.org/2/library/os.html#os.isatty
  http://docs.python.org/3.4/library/os.html#os.isatty


C:\>py -c "import os; print os.isatty(0)"
True

C:\>echo "x" | py -c "import os; print os.isatty(0)"
False

C:\>py -c "import os; print os.isatty(0)" | more
True

Are there tests for this?

None that I know of.

> Are there tests for this?

Not sure what you mean: there are several tests using isatty() in test suite.

Regardless, there is no #ifdef around the isatty() definition in posixmodule.c, so I can only assume it exists on all platforms.

isatty is a part of of POSIX sub-system at Windows > 5.x (AKA 2000) [1] (file handling equivalents [2]). I think, we need to remove availability note here.

[1] http://msdn.microsoft.com/en-us/library/f4s0ddew.aspx
[2] http://msdn.microsoft.com/en-us/library/kdfaxaay.aspx

Agree

New changeset d5c5ac33b9a1 by Senthil Kumaran in branch '2.7':
os.isatty is not Unix only. Correct the wrong documentation.
http://hg.python.org/cpython/rev/d5c5ac33b9a1

I have corrected the documentation. Thanks for raising this issue, anatoly techtonik.

Why only changing Python 2 documentation?

http://docs.python.org/dev/library/os.html#os.isatty
still mention "Availability: Unix."

I had removed them in all. Something must have gone wrong if still present or I did a mistake.


changeset:   85594:678e3c0d2d99
parent:      85591:c116b658aede
parent:      85593:14ba90816930
user:        Senthil Kumaran <senthil@uthcode.com>
date:        Sat Sep 07 11:30:04 2013 -0700
files:       Doc/library/os.rst
description:
merge from 3.3

Removing the mention of os.isatty mention as Unix only
Correct the wrong documentation.


changeset:   85593:14ba90816930
branch:      3.3
parent:      85589:dd669daad7de
user:        Senthil Kumaran <senthil@uthcode.com>
date:        Sat Sep 07 11:28:58 2013 -0700
files:       Doc/library/os.rst
description:
Removing the mention of os.isatty mention as Unix only
Correct the wrong documentation.


changeset:   85592:d5c5ac33b9a1
branch:      2.7
parent:      85588:523cfc78847c
user:        Senthil Kumaran <senthil@uthcode.com>

Senthil: your 3.3->default merge removed the Availability from fpathconf().

Georg: Thanks for spotting. I feel bad for the mistake. I shall correct it.

New changeset 2b7f11ba871c by Senthil Kumaran in branch '3.3':
Correcting the mistake in 14ba90816930
http://hg.python.org/cpython/rev/2b7f11ba871c

New changeset e839e524a7d5 by Senthil Kumaran in branch 'default':
Correcting the mistake in 678e3c0d2d99
http://hg.python.org/cpython/rev/e839e524a7d5

Fixed now. Ascertained myself by doing hg diff -r tip^ -U 10 on local commits before pushing. :-)

I found a little difference in isatty implementaions:

Windows
Determines whether a file descriptor is associated with a character device [1]

Unix
Test whether a file descriptor refers to a terminal [2]

So, we having a same behavior for pipes, but different for I/O redirection with pseudo-character devices:

$ ./python -c "import os;print(os.isatty(0))" < /dev/null
False

e:\PCbuild>python_d.exe -c "import os;print(os.isatty(0))" < NUL
True

Other pseudo devices works simular:
e:\PCbuild>python_d.exe -c "import os;print(os.isatty(0))" < CON
True

I having a snippet to fix that, should I open a new issue for patch?


[1] http://msdn.microsoft.com/en-us/library/f4s0ddew.aspx
[2] http://man7.org/linux/man-pages/man3/isatty.3.html

Hello Dmi,

> I having a snippet to fix that, should I open a new issue for patch?

Please open a new issue.

Thanks!

>
> > I having a snippet to fix that, should I open a new issue for patch?
>
> Please open a new issue.
>

Reference is welcome.