On Mar 18, 3:34 pm, "C. Titus Brown" <c...@msu.edu> wrote:
> -> > Have we decided anything about logging, as Istvan established in his
> -> > branch? I'd like to get rid of explicit writes to sys.stderr, in
> -> > particular.
> ->
> -> Seems like a worthy goal. Has anyone entered an issue for this in the
> -> tracker? I'm not aware that anyone has explicitly proposed this for
> -> 0.8.
>
> Istvan? How much work would this be, do you think?
There is an issue in the tracker for this:
http://code.google.com/p/pygr/issues/detail?id=61
I'd say that to get it incorporated the logger module now currently
under tests/testlib/logger.py would need to be copied/moved to the
main pygr package, then each sys.stderr message would need be replaced
with a call to logger.debug(), info(), warn() or error().
Probably it's best if only one module is migrated at once, to see how
it works out in practice.
The issue above also mentions the verbosity of these messages that
would be best to be made shorter. It is fairly straightforward to do,
all it needs some on-the-fly decision making on what severity level
corresponds to each of the messages. (severity levels rise in the
order listed above).
The way I typically do it is that I have debug messages be littered
throughout the code but these are suppressed by default and get turned
on only when testing with higher verbosity modes (1 or 2). Info and
above are printed by default.
Istvan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pygr-dev" group.
To post to this group, send email to pygr-dev@googlegroups.com
To unsubscribe from this group, send email to
pygr-dev+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
