[yt-dev] Kill logging in the notebook?

[Anthony Scopatz]

I am +1 on this.


On Mon, May 20, 2013 at 10:34 PM, Nathan Goldbaum <nathan12343 at gmail.com>wrote:

> Seems like killing logging in the notebook entirely is overdoing it.
>
> How about defining a new config parameter NotebookLogLevel which sets the
> log level in the notebook?  This way a user can straightforwardly set their
> preference without overwriting the default behavior when using yt from the
> command line.
>
> I would make the default log level relatively high to avoid excessive
> logging in the notebook, but I understand that other people use the logging
> information more than I do so that might not be the best choice.
>
> On May 20, 2013, at 8:25 PM, Sam Skillman <samskillman at gmail.com> wrote:
>
> I think I'm -0 on it since sometimes all you get is whatever was in the
> log to help debug an issue since its tough (impossible?) to get a pdb-like
> session going in a notebook.  Also, the info lines are actually there for a
> reason.  If loglevel isn't 20 by default, maybe we should just change that?
>
> Sam
>
>
> On Mon, May 20, 2013 at 5:07 PM, Christopher Moody <chrisemoody at gmail.com>wrote:
>
>> -1
>> I actually totally disagree. I really like and use the yt logging
>> extensively inside iPython notebook. My workflow is biased towards a lot of
>> frontend-heavy stuff, and it's useful to know when any of that is wonky
>> enough to be logged, but not throw errors. Besides, you can just double
>> click on the side bar to hide a cell's output -- although I can see how
>> that's not helpful if you're plotting.
>>
>> I'd compromise if we can set a separate logging level for the notebook.
>> Then I can change the default for myself. Probably also not hard to do?
>>
>> chris
>>
>>
>> On Mon, May 20, 2013 at 3:56 PM, Casey W. Stark <caseywstark at gmail.com>wrote:
>>
>>> I agree, +1.
>>>
>>>
>>> On Mon, May 20, 2013 at 3: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
>>>>
>>>
>>>
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>>>
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20130521/961f9c0b/attachment.html>