Robert,
> >> There's no definition of "context" --- the first example uses the
> >> string 'czar' and I don't know how that's associated with a logger. If
> >> it needs to be created explicitly from a config file I think we have a
> >> problem.
> >
> > A context is just a way of creating a relative logger name that
> > is pushed/popped (with RAII now). "czar" is just the addition to the
> > logger name path (i.e. default_path = default_path + ".czar"). This new
> > name can be used in the config file, but it is not created from the
> > config file.
>
> So is the logger created for me?
Yes. A logger is created whenever you first refer to it in a
LOG() macro or create its name with a logging context.
> >> The performance of formatted output looks worrying.
> >
> > Bill is working on this for boost::format. Do you find the snprintf timings to be inadequate, too?
>
> I thought that they were OK, but I don't see that on the new page.
It's in Bill's recent E-mail that has not yet been incorporated
into the page.
> I'd like a complete example of what is really being proposed (see below). Please.
How about we turn this around and have you give us an example of
code where you'd like to log stuff, and we'll show you how to do it?
> >>> I think we need to be able to change logging levels from an
> >>> interactive python prompt.
> >>>
> >>> This is probably supported, but with debug("afw.image", 1, ...)
> >>> debug("afw.image.fitsio", 2, ...) Can I enable afw debug logging
> >>> at level 1 (which applies to afw.image and afw.image.fitsio),
> >>> then switch afw.image to 2 (which also applies to
> >>> afw.image.fitsio), and then change afw.image.fitsio to yet
> >>> another log level?
> >>
> >> Can you provide a complete example to illustrate this?
> >
> > setLevel("afw.image", 1)
> > setLevel("afw.image", 2)
> > setLevel("afw.image.fitsio", 3)
>
> That's not complete. How many loggers are involved? How were they created? I'm sorry, but clear complete examples are very helpful.
Two. You created them by your debug() calls.
--
Kian-Tat Lim, LSST Data Management, [log in to unmask]
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
|