OpenERP 5.0.0-3: messages still going to console with log enabled

Bug #343493 reported by Gerry Reno
2
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Invalid
Undecided
Unassigned
psycopg
New
Undecided
Unassigned

Bug Description

Messages are appearing on the console even when logging is enabled.

Eg:

[ ~]# Closing connection <connection object at 0x968e1b8; dsn: 'host=192.168.1.230 port=5432 user=openerp dbname=template1', closed: 0>
Closing connection <connection object at 0x968dbd0; dsn: 'host=192.168.1.230 port=5432 user=openerp dbname=template1', closed: 0>
Closing connection <connection object at 0x968d818; dsn: 'host=192.168.1.230 port=5432 user=openerp dbname=template1', closed: 0>
Closing connection <connection object at 0x98184e8; dsn: 'host=192.168.1.230 port=5432 user=openerp dbname=template1', closed: 0>

Revision history for this message
Christophe Simonis (OpenERP) (kangol) wrote :

Bug comes from psycopg2.

Changed in openobject-server:
status: New → Invalid
Revision history for this message
Gerry Reno (greno-verizon) wrote : Re: [Bug 343493] Re: OpenERP 5.0.0-3: messages still going to console with log enabled

Christophe (OpenERP) wrote:
> Bug comes from psycopg2.
>
> ** Also affects: psycopg
> Importance: Undecided
> Status: New
>
> ** Changed in: openobject-server
> Status: New => Invalid
>
>
This is affecting OpenERP behavior. Did you have an open ticket on pycopg2?

Regards,
Gerry

Revision history for this message
Federico Di Gregorio (fog) wrote :

The message comes from pool.py. WIll be removed before next release (already fixed on psycopg trunk.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers