[issue18846] python.exe stdout stderr issues again
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 stderr to null [out]> Python 3.3 has exactly the same issue. Python 3.4alpha now, although it gives the correct output with the --version switch...: [ in]>python --version 1> null [out]> [ in]>python --version 2> null [out]>Python 3.4.0a1 ...still invoking a simple pyton.exe (switchless), prints its default output to stderr: [ in]>python 1> null [out]>Python 3.4.0a1 (v3.4.0a1:46535f65e7f3, Aug 3 2013, 22:59:31) [MSC v.1600 32 bit (Intel)] on win32 [out]>Type "help", "copyright", "credits" or "license" for more information. [out]>>> [ in]>python 2> null [out]>>> Some notes/refs: Incomplete fix in 3.4a http://bugs.python.org/issue18338 -- components: Interpreter Core messages: 196257 nosy: SSmith priority: normal severity: normal status: open title: python.exe stdout stderr issues again type: behavior versions: Python 2.7, Python 3.3, Python 3.4 ___ Python tracker <http://bugs.python.org/issue18846> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18846] python.exe stdout stderr issues again
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 (v3.4.0a1:46535f65e7f3, Aug 3 2013, 22:59:31) [MSC v.1600 32 bit (Intel)] on win32 [out]>Type "help", "copyright", "credits" or "license" for more information. [out]>>> [ in]>python 2> null [out]>>> -- ___ Python tracker <http://bugs.python.org/issue18846> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18846] python.exe stdout stderr issues again
SSmith added the comment: r/3.4b4/3.4b3 -- ___ Python tracker <http://bugs.python.org/issue18846> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18846] python.exe stdout stderr issues again
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 launching a 'nested' powershell interpreter too. You also direct python.exe verbose output to stderr too. If I uncderstand the 'problem' correctly, it seems that having to choose from just 2 output channels leads to compromises like these. Thanks for your time and apologies for bumping this twice! -- ___ Python tracker <http://bugs.python.org/issue18846> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
