Duplicate lines in logging from SQLAlchemy

$ glance-registry --log-config=/etc/glance/logging.cnf
2011-03-31 17:11:47,016 INFO sqlalchemy.engine.base.Engine.0x...5590 PRAGMA table_info("images")
2011-03-31 17:11:47,017 INFO sqlalchemy.engine.base.Engine.0x...5590 ()
2011-03-31 17:11:47,017 INFO sqlalchemy.engine.base.Engine.0x...5590 PRAGMA table_info("image_properties")
2011-03-31 17:11:47,017 INFO sqlalchemy.engine.base.Engine.0x...5590 ()

# cat glance.log
2011-03-31 17:11:47,016 sqlalchemy.engine.base.Engine.0x...5590: INFO base _cursor_execute PRAGMA table_info("images")
2011-03-31 17:11:47,017 sqlalchemy.engine.base.Engine.0x...5590: INFO base _cursor_execute ()
2011-03-31 17:11:47,017 sqlalchemy.engine.base.Engine.0x...5590: INFO base _cursor_execute PRAGMA table_info("image_properties")
2011-03-31 17:11:47,017 sqlalchemy.engine.base.Engine.0x...5590: INFO base _cursor_execute ()
2011-03-31 17:11:47,019 eventlet.wsgi.server: DEBUG wsgi write (1936) wsgi starting up on http://0.0.0.0:9191/

Look explanation here: http://www.sqlalchemy.org/docs/core/engines.html#configuring-logging
The echo flags present as keyword arguments to create_engine() and others as well as the echo property on Engine, when set to True, will first attempt to ensure that logging is enabled. Unfortunately, the logging module provides no way of determining if output has already been configured (note we are referring to if a logging configuration has been set up, not just that the logging level is set). For this reason, any echo=True flags will result in a call to logging.basicConfig() using sys.stdout as the destination. It also sets up a default format using the level name, timestamp, and logger name. Note that this configuration has the affect of being configured in addition to any existing logger configurations. Therefore, when using Python logging, ensure all echo flags are set to False at all times, to avoid getting duplicate log lines.