From: Erlend E. Aasland Date: Fri, 19 Aug 2022 08:18:08 +0000 (+0200) Subject: Docs: Fix markup of module name in sqlite3 docs (#96115) X-Git-Tag: v3.12.0a1~605 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ee9f22d3464308566c63e972133ebf71b7664baa;p=thirdparty%2FPython%2Fcpython.git Docs: Fix markup of module name in sqlite3 docs (#96115) --- diff --git a/Doc/library/sqlite3.rst b/Doc/library/sqlite3.rst index 508505ca0507..6413d8859180 100644 --- a/Doc/library/sqlite3.rst +++ b/Doc/library/sqlite3.rst @@ -18,13 +18,13 @@ SQLite for internal data storage. It's also possible to prototype an application using SQLite and then port the code to a larger database such as PostgreSQL or Oracle. -The sqlite3 module was written by Gerhard Häring. It provides an SQL interface +The :mod:`!sqlite3` module was written by Gerhard Häring. It provides an SQL interface compliant with the DB-API 2.0 specification described by :pep:`249`, and requires SQLite 3.7.15 or newer. This document includes four main sections: -* :ref:`sqlite3-tutorial` teaches how to use the sqlite3 module. +* :ref:`sqlite3-tutorial` teaches how to use the :mod:`!sqlite3` module. * :ref:`sqlite3-reference` describes the classes and functions this module defines. * :ref:`sqlite3-howtos` details how to handle specific tasks. @@ -839,7 +839,7 @@ Connection objects ignored. Note that the backend does not only run statements passed to the :meth:`Cursor.execute` methods. Other sources include the :ref:`transaction management ` of the - sqlite3 module and the execution of triggers defined in the current + :mod:`!sqlite3` module and the execution of triggers defined in the current database. Passing ``None`` as *trace_callback* will disable the trace callback.