New submission from SSmith:
python.exe sends its output to stderr instead of stdout.
Writing the following to the command line highlight the issue:
[ in]>python.exe --version 1> null #redirects stdout to null
[out]>Python 2.7.5
[ in]>python.exe --version 2> null #redirects
SSmith added the comment:
Please pay some attention to this. This ISSUE is still valid in 3.4b4! Issue
#18338 resolves only part of the problem. Look at this part of the OP:
invoking python.exe prints its default output to stderr:
[ in]>python 1> null
[out]>Python 3.4.0a1
SSmith added the comment:
r/3.4b4/3.4b3
--
___
Python tracker
<http://bugs.python.org/issue18846>
___
___
Python-bugs-list mailing list
Unsubscribe:
SSmith added the comment:
Interestingly to me, you 're right!
Powershell interpreter does the same. Ironically, failure to launch python
from Powershell ISE(Integrated Scripting Environment) was what triggered this
bug report. And as I see know, PowershellISE doesnt support launchi
