Update the mysql-connector-python docs for now

mysql-connector-python still seems to have issues with binary datatypes
but the other issues here, with the possible exception of the deadlock
still being investigated, seem to have been resolved in the recent
8.x series of mysql-connector-python.   The driver is still not
recommended due to these issues however we don't need a special
class of warnings at this point.

Change-Id: I2d59e76df5e84b34e318a24b468626900c39da46
References: #4531
(cherry picked from commit 312d529dbbaa9bb7d8d804280cb39797c6402931)

diff --git a/lib/sqlalchemy/dialects/mysql/mysqlconnector.py b/lib/sqlalchemy/dialects/mysql/mysqlconnector.py
index 90bb95d28ff7342e291908a42f7ea4cd2ed260ff..ef76be02cc8597f3fe4be342e80a4905bf18e9c7 100644 (file)
--- a/lib/sqlalchemy/dialects/mysql/mysqlconnector.py
+++ b/lib/sqlalchemy/dialects/mysql/mysqlconnector.py
@@ -10,40 +10,9 @@ r"""
     :name: MySQL Connector/Python
     :dbapi: myconnpy
     :connectstring: mysql+mysqlconnector://<user>:<password>@<host>[:<port>]/<dbname>
-    :url: http://dev.mysql.com/downloads/connector/python/
+    :url: https://pypi.org/project/mysql-connector-python/
 
 
-Current Issues
---------------
-
-The mysqlconnector driver has many issues that have gone unresolved
-for many years and it recommended that mysqlclient or pymysql be used
-if possible; as of June 27, 2018:
-
-* the values in cursor.description are randomly sent as either bytes
-  or text with no discernible pattern, so the dialect must test these
-  individually and attempt to decode
-
-* has been observed to leak interpreter memory (likely at the C code level)
-  under scenarios that do not leak memory when using mysqlclient
-
-* Under Python 2, the driver does not support SQL statements that contain
-  non-ascii characters within the SQL text, making it impossible to support
-  schema objects with non-ascii names; an ascii encoding error is raised.
-
-* additional random bytes-returned issues occur when running under MySQL 8.0
-  only
-
-* The driver does not accept the "utf8mb4" or "utf8mb3" charset parameters,
-  only "utf8", even though MySQL itself has deprecated this symbol
-
-* The driver produces deadlocks when trying to make use of SELECT..FOR UPDATE,
-  the reason is unknown.
-
-This list should be updated as these issues are resolved either in the
-upstream mysql-connector-python driver or if appropriate usage patterns
-are contributed to SQLAlchemy.
-
 """  # noqa
 
 import re