execsql2 2.1.1__tar.gz → 2.1.2__tar.gz

{execsql2-2.1.1 → execsql2-2.1.2}/.pre-commit-config.yaml

@@ -18,7 +18,7 @@ repos:
       - id: gitleaks
   # uv lockfile management
   - repo: https://github.com/astral-sh/uv-pre-commit
-    rev: 0.10.12
+    rev: 0.11.1
     hooks:
       - id: uv-lock
   # Base hooks
@@ -47,6 +47,7 @@ repos:
           - mdformat-mkdocs==5.1.1
         exclude: |
           (?x)^(
+            docs/api/.*|
             docs/metacommands\.md|
             docs/documentation\.md|
             docs/examples\.md

{execsql2-2.1.1 → execsql2-2.1.2}/.readthedocs.yaml

@@ -9,7 +9,8 @@ build:
     python: "3.13"
   jobs:
     install:
-      - pip install zensical
+      - pip install zensical mkdocstrings-python
+      - pip install -e .
     pre_build:
       - cp CHANGELOG.md docs/change_log.md
     build:

{execsql2-2.1.1 → execsql2-2.1.2}/CHANGELOG.md

@@ -13,6 +13,22 @@ ______________________________________________________________________
 
 ______________________________________________________________________
 
+## [2.1.2] - 2026-03-25
+
+### Changed
+
+- Added PyPI version, Python versions, license, and Read the Docs badges to `README.md`.
+
+### Fixed
+
+- Read the Docs build: added `mkdocstrings-python` and editable project install to `.readthedocs.yaml` so `mkdocstrings` can resolve API references.
+
+- Fixed escaped underscore in `docs/api/cli.md` (`\_run` → `_run`) that caused `mkdocstrings` to fail resolving `execsql.cli._run`.
+
+- Excluded `docs/api/` from `mdformat` pre-commit hook to prevent it from re-escaping underscores in `mkdocstrings` `:::` directives.
+
+______________________________________________________________________
+
 ## [2.1.1] - 2026-03-25
 
 ### Added

{execsql2-2.1.1 → execsql2-2.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: execsql2
-Version: 2.1.1
+Version: 2.1.2
 Summary: Runs a SQL script against a PostgreSQL, SQLite, MariaDB/MySQL, DuckDB, Firebird, MS-Access, MS-SQL-Server, or Oracle database, or an ODBC DSN. Provides metacommands to import and export data, copy data between databases, conditionally execute SQL and metacommands, and dynamically alter SQL and metacommands with substitution variables.
 Project-URL: Repository, https://github.com/geocoug/execsql
 Project-URL: Issues, https://github.com/geocoug/execsql/issues
@@ -105,7 +105,8 @@ Description-Content-Type: text/markdown
 > Not recommended for production use. For the stable upstream release, see [execsql](https://execsql.readthedocs.io/).
 
 <div align="center">
-![execsql logo](https://execsql2.readthedocs.io/en/latest/images/execsql_logo_01.png)
+
+<img src="https://execsql2.readthedocs.io/en/latest/images/execsql_logo_01.png" alt="execsql logo">
 
 *Multi-DBMS SQL script processor.*
 
@@ -115,6 +116,10 @@ Description-Content-Type: text/markdown
 
 [![CI/CD](https://github.com/geocoug/execsql/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/geocoug/execsql/actions/workflows/ci-cd.yml)
 [![codecov](https://codecov.io/gh/geocoug/execsql/graph/badge.svg)](https://codecov.io/gh/geocoug/execsql)
+[![Docs](https://readthedocs.org/projects/execsql2/badge/)](https://execsql2.readthedocs.io/)
+[![PyPI](https://img.shields.io/pypi/v/execsql2)](https://pypi.org/project/execsql2/)
+[![Python](https://img.shields.io/pypi/pyversions/execsql2)](https://pypi.org/project/execsql2/)
+[![License](https://img.shields.io/pypi/l/execsql2)](https://pypi.org/project/execsql2/)
 [![Downloads](https://pepy.tech/badge/execsql2/month)](https://pepy.tech/project/execsql2)
 
 </div>

{execsql2-2.1.1 → execsql2-2.1.2}/README.md

@@ -5,7 +5,8 @@
 > Not recommended for production use. For the stable upstream release, see [execsql](https://execsql.readthedocs.io/).
 
 <div align="center">
-![execsql logo](https://execsql2.readthedocs.io/en/latest/images/execsql_logo_01.png)
+
+<img src="https://execsql2.readthedocs.io/en/latest/images/execsql_logo_01.png" alt="execsql logo">
 
 *Multi-DBMS SQL script processor.*
 
@@ -15,6 +16,10 @@
 
 [![CI/CD](https://github.com/geocoug/execsql/actions/workflows/ci-cd.yml/badge.svg)](https://github.com/geocoug/execsql/actions/workflows/ci-cd.yml)
 [![codecov](https://codecov.io/gh/geocoug/execsql/graph/badge.svg)](https://codecov.io/gh/geocoug/execsql)
+[![Docs](https://readthedocs.org/projects/execsql2/badge/)](https://execsql2.readthedocs.io/)
+[![PyPI](https://img.shields.io/pypi/v/execsql2)](https://pypi.org/project/execsql2/)
+[![Python](https://img.shields.io/pypi/pyversions/execsql2)](https://pypi.org/project/execsql2/)
+[![License](https://img.shields.io/pypi/l/execsql2)](https://pypi.org/project/execsql2/)
 [![Downloads](https://pepy.tech/badge/execsql2/month)](https://pepy.tech/project/execsql2)
 
 </div>

{execsql2-2.1.1 → execsql2-2.1.2}/docs/api/cli.md

@@ -16,6 +16,6 @@ members: false
 
 ## Core execution
 
-::: execsql.cli.\_run
+::: execsql.cli._run
 options:
 show_signature_annotations: false

{execsql2-2.1.1 → execsql2-2.1.2}/docs/index.md

@@ -8,17 +8,17 @@
 
 You can use *execsql* to:
 
-> - Import data from text files and spreadsheets into a database.
-> - Export tables and views to text files, OpenDocument spreadsheets, HTML, JSON, LaTeΧ, XML, or 17 other data formats.
-> - Copy data between different databases, even databases using different DBMSs.
-> - Display tables or views on the terminal or in a GUI dialog window.
-> - Export data using template processors to produce non-tabular output with customized format and contents.
-> - Conditionally execute different SQL commands and metacommands based on the DBMS in use, the database in use, data values, user input, and other conditions.
-> - Execute blocks of SQL statements and metacommands repeatedly, using any of three different looping methods.
-> - Prompt the user to select files or directories, answer questions, or enter data values.
-> - Allow the user to visually compare two tables or views.
-> - Serve data tables to a web application when used as a CGI script.
-> - Write messages to the console or to a file during the processing of a SQL script. These messages can be used to display the progress of the script or create a custom log of the operations that have been carried out or results obtained. Status messages and data exported in text format can be combined in a single text file. Data tables can be exported in a text format that is compatible with Markdown pipe tables, so that script output can be converted into a variety of document formats (see [Example 8](examples.md#example8) and [Example 11](examples.md#example11)).
+- Import data from text files and spreadsheets into a database.
+- Export tables and views to text files, OpenDocument spreadsheets, HTML, JSON, LaTeΧ, XML, or 17 other data formats.
+- Copy data between different databases, even databases using different DBMSs.
+- Display tables or views on the terminal or in a GUI dialog window.
+- Export data using template processors to produce non-tabular output with customized format and contents.
+- Conditionally execute different SQL commands and metacommands based on the DBMS in use, the database in use, data values, user input, and other conditions.
+- Execute blocks of SQL statements and metacommands repeatedly, using any of three different looping methods.
+- Prompt the user to select files or directories, answer questions, or enter data values.
+- Allow the user to visually compare two tables or views.
+- Serve data tables to a web application when used as a CGI script.
+- Write messages to the console or to a file during the processing of a SQL script. These messages can be used to display the progress of the script or create a custom log of the operations that have been carried out or results obtained. Status messages and data exported in text format can be combined in a single text file. Data tables can be exported in a text format that is compatible with Markdown pipe tables, so that script output can be converted into a variety of document formats (see [Example 8](examples.md#example8) and [Example 11](examples.md#example11)).
 
 Different DBMSs and DBMS-specific client programs provide different and incompatible extensions to SQL, ordinarily to allow interactions with the file system and to allow conditional tests and looping. Some DBMSs do not have any native extensions of this sort. *execsql* provides these features, as well as features for user interaction, in an identical fashion for all supported DBMSs. This allows standardization of the SQL scripting language used for different types of database management systems.
 

{execsql2-2.1.1 → execsql2-2.1.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "execsql2"
-version = "2.1.1"
+version = "2.1.2"
 description = "Runs a SQL script against a PostgreSQL, SQLite, MariaDB/MySQL, DuckDB, Firebird, MS-Access, MS-SQL-Server, or Oracle database, or an ODBC DSN. Provides metacommands to import and export data, copy data between databases, conditionally execute SQL and metacommands, and dynamically alter SQL and metacommands with substitution variables."
 readme = { file = "README.md", content-type = "text/markdown" }
 license = { file = "LICENSE.txt" }
@@ -153,7 +153,7 @@ skip-magic-trailing-comma = false
 line-ending = "auto"
 
 [tool.bumpversion]
-current_version = "2.1.1"
+current_version = "2.1.2"
 commit = true
 commit_args = "--no-verify"
 tag = true

{execsql2-2.1.1 → execsql2-2.1.2}/uv.lock

@@ -657,7 +657,7 @@ wheels = [
 
 [[package]]
 name = "execsql2"
-version = "2.1.1"
+version = "2.1.2"
 source = { editable = "." }
 dependencies = [
     { name = "rich" },