From 1322edc7b1effb5bad411742b997cb2103eedfc2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Tue, 3 May 2016 18:29:41 +0300 Subject: Let logging format messages on demand, use warning instead of deprecated warn --- lib/sqlalchemy/events.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib/sqlalchemy/events.py') diff --git a/lib/sqlalchemy/events.py b/lib/sqlalchemy/events.py index c679db37d..e99c5b5e5 100644 --- a/lib/sqlalchemy/events.py +++ b/lib/sqlalchemy/events.py @@ -464,7 +464,7 @@ class ConnectionEvents(event.Events): def before_cursor_execute(conn, cursor, statement, parameters, context, executemany): - log.info("Received statement: %s" % statement) + log.info("Received statement: %s", statement) engine = create_engine('postgresql://scott:tiger@localhost/test') event.listen(engine, "before_cursor_execute", before_cursor_execute) @@ -475,7 +475,7 @@ class ConnectionEvents(event.Events): @event.listens_for(conn, 'before_cursor_execute') def before_cursor_execute(conn, cursor, statement, parameters, context, executemany): - log.info("Received statement: %s" % statement) + log.info("Received statement: %s", statement) When the methods are called with a `statement` parameter, such as in :meth:`.after_cursor_execute`, :meth:`.before_cursor_execute` and -- cgit v1.2.1