]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commitdiff
fix "entry points"
authorMike Bayer <mike_mp@zzzcomputing.com>
Fri, 30 Sep 2022 20:58:26 +0000 (16:58 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Fri, 30 Sep 2022 20:58:26 +0000 (16:58 -0400)
the formatting here wasn't round tripping without manually
adjusting the indentation.  this suggests that "check" mode
is not doing the exact same thing as "write".  maybe
file.write_text() is changing something.

Change-Id: Ic320800eea7d3333b8a76ede85293c2832c619ed

doc/build/core/connections.rst

index ae4f67de4e278562a39fbe1776df45da9f0da5be..936d83c668f14bc6caa933b99a168093d952a8b8 100644 (file)
@@ -2208,7 +2208,7 @@ to create a new dialect "foodialect://", the steps are as follows:
    via ``foodialect.dialect``.
 3. The entry point can be established in setup.py as follows::
 
-      entry_points = """
+    entry_points = """
         [sqlalchemy.dialects]
         foodialect = foodialect.dialect:FooDialect
         """
@@ -2218,7 +2218,7 @@ an existing SQLAlchemy-supported database, the name can be given
 including a database-qualification.  For example, if ``FooDialect``
 were in fact a MySQL dialect, the entry point could be established like this::
 
-      entry_points = """
+    entry_points = """
         [sqlalchemy.dialects]
         mysql.foodialect = foodialect.dialect:FooDialect
         """