From 8b08b1a35b85c24349226c34e6834f4f60db3c6f Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 3 Feb 2014 12:04:51 -0500 Subject: - Fixed bug which prevented MySQLdb-based dialects (e.g. pymysql) from working in Py3K, where a check for "connection charset" would fail due to Py3K's more strict value comparison rules. The call in question wasn't taking the database version into account in any case as the server version was still None at that point, so the method overall has been simplified to rely upon connection.character_set_name(). [ticket:2933] --- lib/sqlalchemy/dialects/mysql/pymysql.py | 1 + 1 file changed, 1 insertion(+) (limited to 'lib/sqlalchemy/dialects/mysql/pymysql.py') diff --git a/lib/sqlalchemy/dialects/mysql/pymysql.py b/lib/sqlalchemy/dialects/mysql/pymysql.py index 74de09c4d..7989203cf 100644 --- a/lib/sqlalchemy/dialects/mysql/pymysql.py +++ b/lib/sqlalchemy/dialects/mysql/pymysql.py @@ -31,6 +31,7 @@ class MySQLDialect_pymysql(MySQLDialect_mysqldb): if py3k: supports_unicode_statements = True + @classmethod def dbapi(cls): return __import__('pymysql') -- cgit v1.2.1