[IPython-dev] Why are stdout and stderr sent to /dev/null by default in kernels?

[MinRK]

I think we only do that when sys.executable is pythonw.exe, because the
pipes fill up and cause the subprocess to hang after 1k of output is
produced. We don’t redirect output to devnull in most cases.

In the IPython kernel, sys.stdout and sys.stderr are redirected over zmq,
which initially doesn’t get received by anyone, so rarely shows up in UI
(depending on frontend). If you want to see it in the terminal, you have to
use sys.__stdout__ and sys.__stderr__.

-MinRK
​

On Thu, Jul 16, 2015 at 9:21 AM, ssanderson <ssanderson at quantopian.com>
wrote:

> This is a pain for developing extensions, and I can't think of any reason I
> would want to ignore kernel stdout/stderr, so I'm curious what the
> perceived
> benefits of this are.
>
> -Scott
>
>
>
> --
> View this message in context:
> http://python.6.x6.nabble.com/Why-are-stdout-and-stderr-sent-to-dev-null-by-default-in-kernels-tp5166925.html
> Sent from the IPython - Development mailing list archive at Nabble.com.
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150716/be927c57/attachment.html>