From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Fri, 30 Sep 2022 21:08:06 +0000 (-0400)
Subject: interim adjustment to code that's not staying formatted
X-Git-Tag: rel_2_0_0b1~26
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=befa8e92675dea992423011b929dfc7ca45de6b6;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

interim adjustment to code that's not staying formatted

@caselit is fixing this but i just need the build
to pass for the moment

Change-Id: I1c39304c5541ac6f09a80fc157f86f1c86421235
---

diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst
index 936d83c668..671d504548 100644
--- a/doc/build/core/connections.rst
+++ b/doc/build/core/connections.rst
@@ -2209,9 +2209,9 @@ to create a new dialect "foodialect://", the steps are as follows:
 3. The entry point can be established in setup.py as follows::
 
     entry_points = """
-        [sqlalchemy.dialects]
-        foodialect = foodialect.dialect:FooDialect
-        """
+          [sqlalchemy.dialects]
+          foodialect = foodialect.dialect:FooDialect
+          """
 
 If the dialect is providing support for a particular DBAPI on top of
 an existing SQLAlchemy-supported database, the name can be given
@@ -2219,9 +2219,9 @@ including a database-qualification.  For example, if ``FooDialect``
 were in fact a MySQL dialect, the entry point could be established like this::
 
     entry_points = """
-        [sqlalchemy.dialects]
-        mysql.foodialect = foodialect.dialect:FooDialect
-        """
+            [sqlalchemy.dialects]
+            mysql.foodialect = foodialect.dialect:FooDialect
+            """
 
 The above entrypoint would then be accessed as ``create_engine("mysql+foodialect://")``.