On Thu, Jul 16, 2009 at 03:45:58PM -0700, Marek Szuba wrote: -> On Wed, 15 Jul 2009 20:06:48 -0700 -> "C. Titus Brown" <[email protected]> wrote: -> -> > I kind of agree with you, but I think it's the simplest (lowest-tech) -> > solution. +1. -> 'tis done: -> -> http://github.com/mkszuba/pygr/commit/a6f05ad407433ff4332e3cb3afbabb11e2cffa69 -> -> ('silencio' branch)
Does 'logger.disable(0)' unset the disabling level? There's no documentation anywhere (in the logging module, in 'logger', etc.) that says that's what actually happens ;) I've added a few patches to my own copy of 'silencio' branch. http://github.com/ctb/pygr/commits/silencio/ -- Make the global disable switch work when running 'runtest.run' via import: http://github.com/ctb/pygr/commit/02373d6d0e01d9382189f84b1d14f0a0fe04f4c8 -- Re-enable dots at lowest verbosity settings: it's important to know that something is running on the slower test modules! http://github.com/ctb/pygr/commit/3458619cb5099e75ac80cf9b1a3c6bb5af171cad -- Eliminate formatdb bleed-through: http://github.com/ctb/pygr/commit/5a614baac465ad1b740e32c01fe0d65b03f6fd03 -- Ensure that tests using the XML-RPC server wait for the server to end: http://github.com/ctb/pygr/commit/0385b7c50a7ec0a291fd3ea3b02c118d619aba66 (this eliminates some debugging output that otherwise comes through on my tests.) -- Mask pygr.Data deprecation warning: http://github.com/ctb/pygr/commit/b8204371f5aab4bf7ec6232faa04da3f6389c977 -- cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
