From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 10 Jul 2014 20:10:46 +0000 (-0400)
Subject: - determine the root cause of the mysqlconnector issue, report
X-Git-Tag: rel_1_0_0b1~332^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=0190ede10767ed455255067cac2d309f070cf70c;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

- determine the root cause of the mysqlconnector issue, report
it and move on
---

diff --git a/test/dialect/mysql/test_types.py b/test/dialect/mysql/test_types.py
index 011215492e..1735202167 100644
--- a/test/dialect/mysql/test_types.py
+++ b/test/dialect/mysql/test_types.py
@@ -154,11 +154,10 @@ class TypesTest(fixtures.TestBase, AssertsExecutionResults, AssertsCompiledSQL):
                 res
             )
 
-    # TODO: how on earth does mysqlconnector pass the precision numeric
-    # testse in the generic suite when it fails this??
-    @testing.fails_on(
-        "mysql+mysqlconnector",
-        "unknown issue, possible bug in mysqlconnector")
+    @testing.fails_if(
+        lambda: testing.against("mysql+mysqlconnector")
+        and not util.py3k,
+        "bug in mysqlconnector; http://bugs.mysql.com/bug.php?id=73266")
     @testing.provide_metadata
     def test_precision_float_roundtrip(self):
         t = Table('t', self.metadata,