singularitysql 0.1.0__tar.gz → 0.1.1__tar.gz

{singularitysql-0.1.0 → singularitysql-0.1.1}/PKG-INFO

@@ -1,23 +1,23 @@
 Metadata-Version: 2.4
 Name: singularitysql
-Version: 0.1.0
+Version: 0.1.1
 Summary: SQL Server stored procedure introspection and Pydantic model generator
 Author: Samuel Urrego
 License-Expression: MIT
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: pyodbc>=5.0
-Requires-Dist: pydantic>=2.0
-Requires-Dist: typer>=0.9
-Requires-Dist: tomli>=2.0
+Requires-Dist: pyodbc>=5.3.0
+Requires-Dist: pydantic>=2.13.4
+Requires-Dist: typer>=0.26.0
+Requires-Dist: tomli>=2.4.1
 Requires-Dist: rich>=15.0.0
 Provides-Extra: dev
-Requires-Dist: pytest>=8.0; extra == "dev"
-Requires-Dist: pytest-cov>=5.0; extra == "dev"
-Requires-Dist: pytest-mock>=3.14; extra == "dev"
-Requires-Dist: ruff>=0.4; extra == "dev"
-Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: pytest>=9.0.3; extra == "dev"
+Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
+Requires-Dist: pytest-mock>=3.15.1; extra == "dev"
+Requires-Dist: ruff>=0.15.14; extra == "dev"
+Requires-Dist: mypy>=2.1.0; extra == "dev"
 Dynamic: license-file
 
 <p align="center">
@@ -27,13 +27,13 @@ Dynamic: license-file
 > SQL Server → Pydantic v2. Automatically.
 
 [![CI](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml/badge.svg)](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml)
-[![Python](https://img.shields.io/pypi/pyversions/singularity.svg)](https://pypi.org/project/singularity/)
+[![Python](https://img.shields.io/pypi/pyversions/singularitysql.svg)](https://pypi.org/project/singularitysql/)
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 
-Singularity bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
+SingularitySQL bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```python
@@ -45,17 +45,17 @@ model = generate_model(meta, mode="dynamic")
 # <class 'pydantic.main.UspGetOrders'>
 ```
 
-## Why Singularity?
+## Why SingularitySQL?
 
 **The problem**: You have dozens of complex stored procedures in SQL Server. Calling them from Python means manually writing Pydantic models for every parameter and result set. One typo, and you get a runtime error.
 
-**The solution**: Singularity reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
+**The solution**: SingularitySQL reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
 
 | Approach | Lines of code | Maintainable | Type-safe |
 |---|---|---|---|
 | Manual Pydantic models | 100s–1000s | ❌ | ⚠️ (manual) |
 | Raw dicts / tuples | Fewer | ❌ | ❌ |
-| **Singularity** | **Zero** | ✅ | ✅ |
+| **SingularitySQL** | **Zero** | ✅ | ✅ |
 
 ## Features
 
@@ -73,11 +73,14 @@ model = generate_model(meta, mode="dynamic")
 ## Installation
 
 ```bash
-uv add singularity
+uv add singularitysql
 # or
-pip install singularity
+pip install singularitysql
 ```
 
+> **Windows users**: scripts go into `.venv/Scripts/`, not the global PATH.
+> Activate the virtual environment first, or use `uv run singularity ...` to avoid `command not found` errors.
+
 **Prerequisite**: [ODBC Driver for SQL Server](https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server) (17 or 18).
 
 ## Quick Start
@@ -105,7 +108,7 @@ naming_convention = "snake_case"
 ### 2. Generate models
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```
@@ -124,7 +127,7 @@ from generated_models.dbo_usp_GetOrders import UspGetOrders
 order = UspGetOrders(id=1, customer_name="Acme Corp", total=99.99)
 ```
 
-## Library Usage
+## Python API
 
 ```python
 from singularity import SQLServerIntrospector, generate_model

{singularitysql-0.1.0 → singularitysql-0.1.1}/README.md

@@ -5,13 +5,13 @@
 > SQL Server → Pydantic v2. Automatically.
 
 [![CI](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml/badge.svg)](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml)
-[![Python](https://img.shields.io/pypi/pyversions/singularity.svg)](https://pypi.org/project/singularity/)
+[![Python](https://img.shields.io/pypi/pyversions/singularitysql.svg)](https://pypi.org/project/singularitysql/)
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 
-Singularity bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
+SingularitySQL bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```python
@@ -23,17 +23,17 @@ model = generate_model(meta, mode="dynamic")
 # <class 'pydantic.main.UspGetOrders'>
 ```
 
-## Why Singularity?
+## Why SingularitySQL?
 
 **The problem**: You have dozens of complex stored procedures in SQL Server. Calling them from Python means manually writing Pydantic models for every parameter and result set. One typo, and you get a runtime error.
 
-**The solution**: Singularity reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
+**The solution**: SingularitySQL reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
 
 | Approach | Lines of code | Maintainable | Type-safe |
 |---|---|---|---|
 | Manual Pydantic models | 100s–1000s | ❌ | ⚠️ (manual) |
 | Raw dicts / tuples | Fewer | ❌ | ❌ |
-| **Singularity** | **Zero** | ✅ | ✅ |
+| **SingularitySQL** | **Zero** | ✅ | ✅ |
 
 ## Features
 
@@ -51,11 +51,14 @@ model = generate_model(meta, mode="dynamic")
 ## Installation
 
 ```bash
-uv add singularity
+uv add singularitysql
 # or
-pip install singularity
+pip install singularitysql
 ```
 
+> **Windows users**: scripts go into `.venv/Scripts/`, not the global PATH.
+> Activate the virtual environment first, or use `uv run singularity ...` to avoid `command not found` errors.
+
 **Prerequisite**: [ODBC Driver for SQL Server](https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server) (17 or 18).
 
 ## Quick Start
@@ -83,7 +86,7 @@ naming_convention = "snake_case"
 ### 2. Generate models
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```
@@ -102,7 +105,7 @@ from generated_models.dbo_usp_GetOrders import UspGetOrders
 order = UspGetOrders(id=1, customer_name="Acme Corp", total=99.99)
 ```
 
-## Library Usage
+## Python API
 
 ```python
 from singularity import SQLServerIntrospector, generate_model

{singularitysql-0.1.0 → singularitysql-0.1.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "singularitysql"
-version = "0.1.0"
+version = "0.1.1"
 description = "SQL Server stored procedure introspection and Pydantic model generator"
 readme = "README.md"
 requires-python = ">=3.10"
@@ -10,10 +10,10 @@ authors = [
 ]
 
 dependencies = [
-    "pyodbc>=5.0",
-    "pydantic>=2.0",
-    "typer>=0.9",
-    "tomli>=2.0",
+    "pyodbc>=5.3.0",
+    "pydantic>=2.13.4",
+    "typer>=0.26.0",
+    "tomli>=2.4.1",
     "rich>=15.0.0",
 ]
 
@@ -22,11 +22,11 @@ singularity = "singularity.cli._app:_main"
 
 [project.optional-dependencies]
 dev = [
-    "pytest>=8.0",
-    "pytest-cov>=5.0",
-    "pytest-mock>=3.14",
-    "ruff>=0.4",
-    "mypy>=1.10",
+    "pytest>=9.0.3",
+    "pytest-cov>=7.1.0",
+    "pytest-mock>=3.15.1",
+    "ruff>=0.15.14",
+    "mypy>=2.1.0",
 ]
 
 [tool.pytest.ini_options]
@@ -49,7 +49,7 @@ warn_unused_ignores = true
 ignore_missing_imports = true
 
 [build-system]
-requires = ["setuptools>=68.0"]
+requires = ["setuptools>=82.0.1"]
 build-backend = "setuptools.build_meta"
 
 [tool.setuptools.packages.find]

{singularitysql-0.1.0 → singularitysql-0.1.1}/singularitysql.egg-info/PKG-INFO

@@ -1,23 +1,23 @@
 Metadata-Version: 2.4
 Name: singularitysql
-Version: 0.1.0
+Version: 0.1.1
 Summary: SQL Server stored procedure introspection and Pydantic model generator
 Author: Samuel Urrego
 License-Expression: MIT
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: pyodbc>=5.0
-Requires-Dist: pydantic>=2.0
-Requires-Dist: typer>=0.9
-Requires-Dist: tomli>=2.0
+Requires-Dist: pyodbc>=5.3.0
+Requires-Dist: pydantic>=2.13.4
+Requires-Dist: typer>=0.26.0
+Requires-Dist: tomli>=2.4.1
 Requires-Dist: rich>=15.0.0
 Provides-Extra: dev
-Requires-Dist: pytest>=8.0; extra == "dev"
-Requires-Dist: pytest-cov>=5.0; extra == "dev"
-Requires-Dist: pytest-mock>=3.14; extra == "dev"
-Requires-Dist: ruff>=0.4; extra == "dev"
-Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: pytest>=9.0.3; extra == "dev"
+Requires-Dist: pytest-cov>=7.1.0; extra == "dev"
+Requires-Dist: pytest-mock>=3.15.1; extra == "dev"
+Requires-Dist: ruff>=0.15.14; extra == "dev"
+Requires-Dist: mypy>=2.1.0; extra == "dev"
 Dynamic: license-file
 
 <p align="center">
@@ -27,13 +27,13 @@ Dynamic: license-file
 > SQL Server → Pydantic v2. Automatically.
 
 [![CI](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml/badge.svg)](https://github.com/Samuel-Urrego/Singularity/actions/workflows/ci.yml)
-[![Python](https://img.shields.io/pypi/pyversions/singularity.svg)](https://pypi.org/project/singularity/)
+[![Python](https://img.shields.io/pypi/pyversions/singularitysql.svg)](https://pypi.org/project/singularitysql/)
 [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)
 
-Singularity bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
+SingularitySQL bridges the gap between SQL Server and Python. Connect to your database, point at a stored procedure, and get a **Pydantic v2 model** — as a runtime class or a `.py` file you can commit.
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```python
@@ -45,17 +45,17 @@ model = generate_model(meta, mode="dynamic")
 # <class 'pydantic.main.UspGetOrders'>
 ```
 
-## Why Singularity?
+## Why SingularitySQL?
 
 **The problem**: You have dozens of complex stored procedures in SQL Server. Calling them from Python means manually writing Pydantic models for every parameter and result set. One typo, and you get a runtime error.
 
-**The solution**: Singularity reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
+**The solution**: SingularitySQL reads SQL Server's system catalog (`sys.parameters`, `sp_describe_first_result_set`) and generates the models for you. Zero manual mapping.
 
 | Approach | Lines of code | Maintainable | Type-safe |
 |---|---|---|---|
 | Manual Pydantic models | 100s–1000s | ❌ | ⚠️ (manual) |
 | Raw dicts / tuples | Fewer | ❌ | ❌ |
-| **Singularity** | **Zero** | ✅ | ✅ |
+| **SingularitySQL** | **Zero** | ✅ | ✅ |
 
 ## Features
 
@@ -73,11 +73,14 @@ model = generate_model(meta, mode="dynamic")
 ## Installation
 
 ```bash
-uv add singularity
+uv add singularitysql
 # or
-pip install singularity
+pip install singularitysql
 ```
 
+> **Windows users**: scripts go into `.venv/Scripts/`, not the global PATH.
+> Activate the virtual environment first, or use `uv run singularity ...` to avoid `command not found` errors.
+
 **Prerequisite**: [ODBC Driver for SQL Server](https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server) (17 or 18).
 
 ## Quick Start
@@ -105,7 +108,7 @@ naming_convention = "snake_case"
 ### 2. Generate models
 
 ```bash
-singularity --config config.toml
+singularity generate --config config.toml
 ```
 
 ```
@@ -124,7 +127,7 @@ from generated_models.dbo_usp_GetOrders import UspGetOrders
 order = UspGetOrders(id=1, customer_name="Acme Corp", total=99.99)
 ```
 
-## Library Usage
+## Python API
 
 ```python
 from singularity import SQLServerIntrospector, generate_model

singularitysql-0.1.1/singularitysql.egg-info/requires.txt

@@ -0,0 +1,12 @@
+pyodbc>=5.3.0
+pydantic>=2.13.4
+typer>=0.26.0
+tomli>=2.4.1
+rich>=15.0.0
+
+[dev]
+pytest>=9.0.3
+pytest-cov>=7.1.0
+pytest-mock>=3.15.1
+ruff>=0.15.14
+mypy>=2.1.0

singularitysql-0.1.0/singularitysql.egg-info/requires.txt

@@ -1,12 +0,0 @@
-pyodbc>=5.0
-pydantic>=2.0
-typer>=0.9
-tomli>=2.0
-rich>=15.0.0
-
-[dev]
-pytest>=8.0
-pytest-cov>=5.0
-pytest-mock>=3.14
-ruff>=0.4
-mypy>=1.10