Re: ThreadedConnectionPool and Cherrypy

On Fri, Jun 25, 2010 at 4:02 PM, Joe Abbate <jma-ICVE9uepxrQgpMukQH3QewC/[email protected]> wrote:

> Just to clarify, my application doesn't take any explicit action with
> respect to logging (except for defining log.error_file in the production
> configuration). =A0Therefore, CherryPy is the one that controls logging. =
=A0The
> CP code is here:

I'm taking a look at an application of mine running cherrypy. It seems
the handlers are installed on the cherrypy.access and cherrypy.error
loggers and there is no handler installed on the root logger.
Therefore psycopg pool will install its own regardless of the order of
import. You may disable this using the 2nd or the 3rd of the suggested
workarounds, while we fix the library (if we decide to drop
basicConfig()).

-- Daniele