[yt-dev] Kill logging in the notebook?

[Matthew Turk]

Hi Nathan,

I'm strongly -1 on disabling logging.  Nearly all IO has been pushed
into the logging module -- offhand, all I can think of that doesn't go
through logging is the stuff in various C routines, like the halo
finder.

Having a different level of logging is interesting, but I think
instead of focusing on that we should evaluate what goes into "info"
that should go into "debug".  Pushing for less verbosity by default
overall I think would be a good goal, but it's not clear to me that
disabling all but "warning" and "error" is the right move for the
notebook.

-Matt

On Mon, May 20, 2013 at 6:49 PM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
> Hi all,
>
> I have a quick request for feedback about a change to the way yt.imods works.
>
> I'm of the opinion that the logging, while useful and nice when calling yt from a script or an IPython prompt, makes for a bad UI experience from inside the notebook.  The logs are sent to stderr, so they show up in the notebook output in a scary looking red box.  Worse, vertical space is at a premium on the widescreen displays that most of us use, and the logging output tends to push the results we actually want to see off the bottom of the display.
>
> Fortunately there is an easy fix for this: disable stream logging when running yt from the notebook.  I think this is doable with a one or two line change to yt.imods.
>
> I'm curious if other people agree with me on this - +/- 1?
>
> -Nathan
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org