Phillip J. Eby wrote:
> And how is, say, an SQL connection object supposed to know what the
> "page path" is? That was the whole point of this thread: that without
> passing logger objects around, or having some other dynamic context,
> there's no way for libraries to direct their log information to the
> right place.
Well, this feels pretty odd to me, but I guess each to their own.
Regardless, the problems of wsgi.errors not having any clue about log
levels make it an unappealing prospect to use. Still, there's no problem
with a wsgi application doing its own logging to its own log files, right?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe:
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
