Nicolas: The issue here is a very generic one, but the problem is very
specific. How to clear out the errors depends on the errors in the log.

Deprecation warnings can be hidden. Check out the warnings module ( see
http://docs.python.org/library/warnings.html ).

KeyErrors are bugs in the code somewhere. If it's in your code, fix the bug.
If it's in TG or elsewhere in the stack, file a bug and we'll get it fixed.

The threading stuff means getting a solid handle on Python logging, and that
is decidedly not easy. I've been meaning to do a blog post on it
specifically to help people out. In the meantime, look at
http://docs.python.org/howto/logging.html#logging-advanced-tutorial for some
fairly detailed information. Beyond that, it's just going to require
experimentation.

On Fri, May 6, 2011 at 4:20 AM, NiL <[email protected]> wrote:

> Hi list,
>
>
> While running TG behind Apache, I get loads of output in error.log
> (KeyError, md5 deprecation, threading, ...)
>
> mostly from pylons, and maybe TG
>
> What would be a good setting of logs in production.ini to get rid of
> those outputs while keeping useful logs from my app ?
>
> log = logging.getLogger("myapp")
>
> regards
>
> NIL
>
> --
> You received this message because you are subscribed to the Google Groups
> "TurboGears" 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/turbogears?hl=en.
>
>


-- 
Michael J. Pedersen
My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171
          Yahoo/pedermj2002, MSN/[email protected]
My LinkedIn Profile: http://www.linkedin.com/in/michaeljpedersen

-- 
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en.

Reply via email to