From: LunarShaddow <aflyhorse@hotmail.com>
Date: Fri, 5 May 2017 06:38:41 +0000 (+0800)
Subject: remove ambiguous line breakers to help sphinx identify code block
X-Git-Tag: rel_1_2_0b1~78^2~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8e17496421efe0db8dc52d3f25ca2ef6cc65aab4;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

remove ambiguous line breakers to help sphinx identify code block
---

diff --git a/lib/sqlalchemy/dialects/mysql/base.py b/lib/sqlalchemy/dialects/mysql/base.py
index dc7e3b369b..f1d779e0df 100644
--- a/lib/sqlalchemy/dialects/mysql/base.py
+++ b/lib/sqlalchemy/dialects/mysql/base.py
@@ -205,8 +205,7 @@ Most MySQL DBAPIs offer the option to set the client character set for
 a connection.   This is typically delivered using the ``charset`` parameter
 in the URL, such as::
 
-    e = create_engine("mysql+pymysql://scott:tiger@localhost/\
-test?charset=utf8")
+    e = create_engine("mysql+pymysql://scott:tiger@localhost/test?charset=utf8")
 
 This charset is the **client character set** for the connection.  Some
 MySQL DBAPIs will default this to a value such as ``latin1``, and some
@@ -224,8 +223,7 @@ that includes codepoints more than three bytes in size,
 this new charset is preferred, if supported by both the database as well
 as the client DBAPI, as in::
 
-    e = create_engine("mysql+pymysql://scott:tiger@localhost/\
-test?charset=utf8mb4")
+    e = create_engine("mysql+pymysql://scott:tiger@localhost/test?charset=utf8mb4")
 
 At the moment, up-to-date versions of MySQLdb and PyMySQL support the
 ``utf8mb4`` charset.   Other DBAPIs such as MySQL-Connector and OurSQL
@@ -2105,4 +2103,3 @@ class _DecodingRowProxy(object):
             return item.decode(self.charset)
         else:
             return item
-