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 <rep...@bugs.python.org> <http://bugs.python.org/issue18846> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
