This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author akira
Recipients Thekent, akira, ned.deily, ppperry, roger.serwy, serhiy.storchaka, terry.reedy
Date 2014-10-19.14:47:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413730056.8.0.816946233277.issue11820@psf.upfronthosting.co.za>
In-reply-to
Content
It looks like the issue can be reduced to whether or not to show this
output:

  >>> import os
  >>> os.write(1, b'should we see this in idle?\n')
  should we see this in idle?
  28

assuming sys.__stdout__.fileno() == fileno(stdout) == 1.

If "should we see this in idle?" is shown in idle then the output that
writes to the inherited C stdout such as os.system('ls'), 
subprocess.call('ls') will also be shown automatically.

And in reverse If "should we see this in idle?" should not be shown 
then other C stdout output such as produced by os.system('ls') should 
not be redirected too. The output written to the same file should be
shown/not shown consistently.

  os.write(2, b'the same goes for stderr\n')
History
Date User Action Args
2014-10-19 14:47:36akirasetrecipients: + akira, terry.reedy, ned.deily, roger.serwy, Thekent, serhiy.storchaka, ppperry
2014-10-19 14:47:36akirasetmessageid: <1413730056.8.0.816946233277.issue11820@psf.upfronthosting.co.za>
2014-10-19 14:47:36akiralinkissue11820 messages
2014-10-19 14:47:36akiracreate