From 48f8a831daf53c7315cbd0168ecd23a69c3be538 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Fri, 30 Sep 2022 16:58:26 -0400 Subject: [PATCH] fix "entry points" 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 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst index ae4f67de4e..936d83c668 100644 --- a/doc/build/core/connections.rst +++ b/doc/build/core/connections.rst @@ -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 """ -- 2.47.3