[ZODB-Dev] ZEO trace info

[Guido van Rossum]

> > > Does anyone have a problem if I bump most zLOG.DEBUG to zLOG.TRACE in
> > > the misc ZEO files? A lot of info is written for a single page request,
> > > and it's very hard to see other DEBUG messages in the middle of the ZEO
> > > stuff.
> > 
> > Sure, but as one of the current ZEO developers I'd prefer to review
> > your proposed changes a little.  Can you either provide a patch or
> > just a list of which messages you'd like to see bumped?
> 
> I was thinking of:
> 
> --- connection.py.~1.38.2.3.~	Thu Dec 19 18:44:04 2002
> +++ connection.py	Fri Jan 24 14:34:46 2003
> @@ -213,7 +213,7 @@
>      def handle_reply(self, msgid, flags, args):
>          if __debug__:
>              self.log("recv reply: %s, %s, %s"
> -                     % (msgid, flags, short_repr(args)), level=zLOG.DEBUG)
> +                     % (msgid, flags, short_repr(args)), level=zLOG.TRACE)
>          self.replies_cond.acquire()
>          try:
>              self.replies[msgid] = flags, args
> @@ -387,7 +387,7 @@
>                      del self.replies[msgid]
>                      if __debug__:
>                          self.log("wait(%d): reply=%s" %
> -                                 (msgid, short_repr(reply)), level=zLOG.DEBUG)
> +                                 (msgid, short_repr(reply)), level=zLOG.TRACE)
>                      return reply
>                  if self.is_async():
>                      self.replies_cond.wait(10.0)
> 
> 
> (most of the others are already at level zLOG.TRACE)

OK, done.  (The second was already done in CVS!)

--Guido van Rossum (home page: http://www.python.org/~guido/)