this is python code, we can format

Change-Id: I01aee8b50afe84b8df6154fa73a4375d746cbc02

diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst
index 4f77e1ada95b87ac4a362d1802ae9ae4f01b034d..ae4f67de4e278562a39fbe1776df45da9f0da5be 100644 (file)
--- a/doc/build/core/connections.rst
+++ b/doc/build/core/connections.rst
@@ -2196,9 +2196,6 @@ Multiple result set support is available from a raw DBAPI cursor using the
 Registering New Dialects
 ========================
 
-.. highlight:: ini
-.. format:off
-
 The :func:`_sa.create_engine` function call locates the given dialect
 using setuptools entrypoints.   These entry points can be established
 for third party dialects within the setup.py script.  For example,
@@ -2211,25 +2208,23 @@ 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="""
-      [sqlalchemy.dialects]
-      foodialect = foodialect.dialect:FooDialect
-      """
+      entry_points = """
+        [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
 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
-      """
+      entry_points = """
+        [sqlalchemy.dialects]
+        mysql.foodialect = foodialect.dialect:FooDialect
+        """
 
 The above entrypoint would then be accessed as ``create_engine("mysql+foodialect://")``.
 
-.. format:on
-.. highlight:: python
 
 Registering Dialects In-Process
 -------------------------------