Message209574
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! |
|
Date |
User |
Action |
Args |
2014-01-28 18:47:14 | SSmith | set | recipients:
+ SSmith, benjamin.peterson |
2014-01-28 18:47:14 | SSmith | set | messageid: <1390934834.75.0.406331893096.issue18846@psf.upfronthosting.co.za> |
2014-01-28 18:47:14 | SSmith | link | issue18846 messages |
2014-01-28 18:47:14 | SSmith | create | |
|