sqlty 0.4.0__tar.gz → 0.6.0__tar.gz

{sqlty-0.4.0 → sqlty-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sqlty
-Version: 0.4.0
+Version: 0.6.0
 Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
@@ -12,6 +12,7 @@ Classifier: Programming Language :: Rust
 Classifier: Programming Language :: SQL
 Classifier: Topic :: Software Development :: Code Generators
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Software Development :: Quality Assurance
 Classifier: Topic :: Database
 Classifier: Typing :: Typed
 Requires-Dist: pathspec>=0.12.1
@@ -19,15 +20,15 @@ Requires-Dist: typing-extensions>=4.15.0 ; python_full_version < '3.15'
 Requires-Dist: psycopg>=3.2.12 ; extra == 'psycopg'
 Provides-Extra: psycopg
 License-File: LICENSE
-Summary: Type-safe SQL queries for Python
-Keywords: sql,type-hints,mypy,type-safety,static-analysis,code-generation
+Summary: Type-safe raw SQL for Python: row and parameter types inferred from your SQL and schema, no ORM or database needed
+Keywords: sql,raw-sql,type-safety,type-checking,type-hints,static-analysis,linter,mypy,pyright,ty,postgresql,sqlite,mysql,psycopg,migrations,code-generation,orm-alternative
 Author-email: Jiri Kuncar <jiri.kuncar@gmail.com>
 License-Expression: MIT
 Requires-Python: >=3.14
 Description-Content-Type: text/markdown; charset=UTF-8; variant=GFM
 Project-URL: Changelog, https://github.com/jirikuncar/sqlty/releases
-Project-URL: Documentation, https://jirikuncar.github.io/sqlty/
-Project-URL: Homepage, https://github.com/jirikuncar/sqlty
+Project-URL: Documentation, https://sqlty.kuncar.dev/
+Project-URL: Homepage, https://sqlty.kuncar.dev/
 Project-URL: Issues, https://github.com/jirikuncar/sqlty/issues
 Project-URL: Repository, https://github.com/jirikuncar/sqlty
 
@@ -56,13 +57,14 @@ migration that changes a column is caught in review, not in production.
   (<a href="https://github.com/jirikuncar/sqlty/blob/main/docs/assets/demo.tape">view source</a>)
 </p>
 
-**Documentation: [jirikuncar.github.io/sqlty](https://jirikuncar.github.io/sqlty/)**
+**Documentation: [sqlty.kuncar.dev](https://sqlty.kuncar.dev/)** ·
+**Try it in your browser: [Playground](https://sqlty.kuncar.dev/playground/)**
 
 **Fits if** you write SQL as string literals on Python 3.14+, against
 PostgreSQL, SQLite or MySQL, with a schema dump or SQL migrations in the
 repository. Rows are typed end to end with psycopg 3; with other drivers sqlty
 checks the query and its parameters, and you annotate what the cursor returns
-([Drivers](https://jirikuncar.github.io/sqlty/guide/drivers-and-orms/)).
+([Drivers](https://sqlty.kuncar.dev/guide/drivers-and-orms/)).
 
 > **Beta.** APIs and configuration may change before 1.0. Feedback welcome in
 > [GitHub Issues](https://github.com/jirikuncar/sqlty/issues).
@@ -91,6 +93,8 @@ query = "--sql\nSELECT id, name, email FROM users"
 # rewritten: query = SQL[tuple[int, str, str]]("--sql\nSELECT id, name, email FROM users")
 ```
 
+[Open in playground](https://sqlty.kuncar.dev/playground/#eJw9jcsKwjAURH_lkpWFdiN0o7iI5arFPiRGsZBNSWMN9GGbdiHiv9tQdDGbM8OcNzHt2EtFVkC6UfUv2IAgnme6SojmjBEGHHThQpPXygVV57qCHUtjGI3qjSCiIS4QIx9TZU8ChpQjcLqNcN7AQhcQJhz3yODEwpiyDI6YzZ_A8cYhSadcouhnuFIWHChbLH3f-ZfO2qoKnVdKDtb1bM1Q9spYLNvmrktLyecL_GI_Gw)
+
 `SQL[T]` is a `str` subclass, so the query still runs anywhere a string does,
 and mypy, pyright and ty see `T`. Without a schema, casts such as `id::INTEGER`
 type the columns; a query with neither stays as it is. With a space instead of
@@ -120,14 +124,16 @@ from sqlty import SQL
 query = SQL[tuple[int, str]]("--sql\nSELECT id, email FROM users")
 ```
 
+[Open in playground](https://sqlty.kuncar.dev/playground/#eJw1jUsOgjAURbfy0pEksAGNAyRPYwQ_pQMJdWCgYBNooS0DYty7NMbh_Z37JlZPphJkDaQxugc7dm4G2Q_aOMhvKVdcjZMwM2y9LN00dKKUyoVgnXk8VpxE0TLiXOWYYsJA1iGI_ik72NNLBpMVxnIScEVCILZ6LZl_SyjGDIHFuxR_JVjJGo5nhgekcKXHLKYFnLD44xjeWbDxlFo-O1E5jxm0da0R1tuVVo1svUs-X3IeRJA)
+
 `sqlty check --fix .` updates the type, and your type checker finds every
 caller that now needs a `None` check. `narrow-type` is an error, so CI fails on
 it; an annotation that is only wider than the rows, such as `str | None` for a
 column made `NOT NULL`, is a `stale-type` warning
-([CI](https://jirikuncar.github.io/sqlty/recipes/ci/)). For rolling deploys,
+([CI](https://sqlty.kuncar.dev/recipes/ci/)). For rolling deploys,
 `sqlty breaking --against origin/main` exits 1 when old code breaks on the new
 schema or new code on the old one
-([Breaking schema changes](https://jirikuncar.github.io/sqlty/guide/breaking-changes/)).
+([Breaking schema changes](https://sqlty.kuncar.dev/guide/breaking-changes/)).
 
 ### A row type that doesn't match its query
 
@@ -144,7 +150,7 @@ query = SQL[User]("--sql\nSELECT id::INTEGER, name::TEXT FROM users")
 ```
 
 `TypedDict`, `NamedTuple`, dataclasses and Pydantic models are all checked
-([Row types](https://jirikuncar.github.io/sqlty/guide/row-types/)).
+([Row types](https://sqlty.kuncar.dev/guide/row-types/)).
 
 ### Wrong parameters, misspelled columns
 
@@ -176,11 +182,11 @@ conn.execute(SQL[tuple[str | None]]("--sql\nSELECT email FROM users WHERE id = ?
 conn.execute("--sql\nSELECT emial FROM users")
 ```
 
-`?`, `$1`, `%s` and `:name` placeholders are checked on sqlite3, psycopg and
-asyncpg calls ([Parameters](https://jirikuncar.github.io/sqlty/guide/parameters/)).
+`?`, `$1`, `%s` and `:name` placeholders are checked on sqlite3, aiosqlite,
+psycopg and asyncpg calls ([Parameters](https://sqlty.kuncar.dev/guide/parameters/)).
 These are the mistakes coding agents make: every problem is one
 `file:line: [rule] message` line and a non-zero exit code they can act on, and
-the [sqlty skills](https://jirikuncar.github.io/sqlty/recipes/agents/) teach
+the [sqlty skills](https://sqlty.kuncar.dev/recipes/agents/) teach
 them the conventions. In Claude Code, `/plugin install sqlty --marketplace jirikuncar/sqlty`
 installs them.
 
@@ -196,13 +202,13 @@ sqlty strip .                  # undo: back to plain strings
 
 `rewrite` and `strip` only touch the wrapper, never the SQL, so you can adopt
 sqlty one module at a time and back out. New project:
-[Quickstart](https://jirikuncar.github.io/sqlty/quickstart/). Existing codebase:
-[Migration](https://jirikuncar.github.io/sqlty/recipes/migration/), starting
+[Quickstart](https://sqlty.kuncar.dev/quickstart/). Existing codebase:
+[Migration](https://sqlty.kuncar.dev/recipes/migration/), starting
 with `pg_dump --schema-only app > schema.sql`. In the editor:
-[VS Code](https://jirikuncar.github.io/sqlty/recipes/vscode/).
+[VS Code](https://sqlty.kuncar.dev/recipes/vscode/).
 
 Not a fit for ORMs, SQL built at runtime, or runtime validation;
-[Why SQLTy?](https://jirikuncar.github.io/sqlty/motivation/) compares it with
+[Why SQLTy?](https://sqlty.kuncar.dev/motivation/) compares it with
 sqlc, sqlx, PgTyped and others.
 
 ## About
@@ -213,6 +219,6 @@ developed with AI coding agents, mainly Claude Code; every change is reviewed by
 a maintainer (see the
 [AI-assisted contributions](https://github.com/jirikuncar/sqlty/blob/main/CONTRIBUTING.md#ai-assisted-contributions)
 policy). [Contributing](https://github.com/jirikuncar/sqlty/blob/main/CONTRIBUTING.md) ·
-[Credits](https://jirikuncar.github.io/sqlty/credits/) ·
+[Credits](https://sqlty.kuncar.dev/credits/) ·
 MIT [License](https://github.com/jirikuncar/sqlty/blob/main/LICENSE).
 

{sqlty-0.4.0 → sqlty-0.6.0}/README.md

@@ -23,13 +23,14 @@ migration that changes a column is caught in review, not in production.
   (<a href="https://github.com/jirikuncar/sqlty/blob/main/docs/assets/demo.tape">view source</a>)
 </p>
 
-**Documentation: [jirikuncar.github.io/sqlty](https://jirikuncar.github.io/sqlty/)**
+**Documentation: [sqlty.kuncar.dev](https://sqlty.kuncar.dev/)** ·
+**Try it in your browser: [Playground](https://sqlty.kuncar.dev/playground/)**
 
 **Fits if** you write SQL as string literals on Python 3.14+, against
 PostgreSQL, SQLite or MySQL, with a schema dump or SQL migrations in the
 repository. Rows are typed end to end with psycopg 3; with other drivers sqlty
 checks the query and its parameters, and you annotate what the cursor returns
-([Drivers](https://jirikuncar.github.io/sqlty/guide/drivers-and-orms/)).
+([Drivers](https://sqlty.kuncar.dev/guide/drivers-and-orms/)).
 
 > **Beta.** APIs and configuration may change before 1.0. Feedback welcome in
 > [GitHub Issues](https://github.com/jirikuncar/sqlty/issues).
@@ -58,6 +59,8 @@ query = "--sql\nSELECT id, name, email FROM users"
 # rewritten: query = SQL[tuple[int, str, str]]("--sql\nSELECT id, name, email FROM users")
 ```
 
+[Open in playground](https://sqlty.kuncar.dev/playground/#eJw9jcsKwjAURH_lkpWFdiN0o7iI5arFPiRGsZBNSWMN9GGbdiHiv9tQdDGbM8OcNzHt2EtFVkC6UfUv2IAgnme6SojmjBEGHHThQpPXygVV57qCHUtjGI3qjSCiIS4QIx9TZU8ChpQjcLqNcN7AQhcQJhz3yODEwpiyDI6YzZ_A8cYhSadcouhnuFIWHChbLH3f-ZfO2qoKnVdKDtb1bM1Q9spYLNvmrktLyecL_GI_Gw)
+
 `SQL[T]` is a `str` subclass, so the query still runs anywhere a string does,
 and mypy, pyright and ty see `T`. Without a schema, casts such as `id::INTEGER`
 type the columns; a query with neither stays as it is. With a space instead of
@@ -87,14 +90,16 @@ from sqlty import SQL
 query = SQL[tuple[int, str]]("--sql\nSELECT id, email FROM users")
 ```
 
+[Open in playground](https://sqlty.kuncar.dev/playground/#eJw1jUsOgjAURbfy0pEksAGNAyRPYwQ_pQMJdWCgYBNooS0DYty7NMbh_Z37JlZPphJkDaQxugc7dm4G2Q_aOMhvKVdcjZMwM2y9LN00dKKUyoVgnXk8VpxE0TLiXOWYYsJA1iGI_ik72NNLBpMVxnIScEVCILZ6LZl_SyjGDIHFuxR_JVjJGo5nhgekcKXHLKYFnLD44xjeWbDxlFo-O1E5jxm0da0R1tuVVo1svUs-X3IeRJA)
+
 `sqlty check --fix .` updates the type, and your type checker finds every
 caller that now needs a `None` check. `narrow-type` is an error, so CI fails on
 it; an annotation that is only wider than the rows, such as `str | None` for a
 column made `NOT NULL`, is a `stale-type` warning
-([CI](https://jirikuncar.github.io/sqlty/recipes/ci/)). For rolling deploys,
+([CI](https://sqlty.kuncar.dev/recipes/ci/)). For rolling deploys,
 `sqlty breaking --against origin/main` exits 1 when old code breaks on the new
 schema or new code on the old one
-([Breaking schema changes](https://jirikuncar.github.io/sqlty/guide/breaking-changes/)).
+([Breaking schema changes](https://sqlty.kuncar.dev/guide/breaking-changes/)).
 
 ### A row type that doesn't match its query
 
@@ -111,7 +116,7 @@ query = SQL[User]("--sql\nSELECT id::INTEGER, name::TEXT FROM users")
 ```
 
 `TypedDict`, `NamedTuple`, dataclasses and Pydantic models are all checked
-([Row types](https://jirikuncar.github.io/sqlty/guide/row-types/)).
+([Row types](https://sqlty.kuncar.dev/guide/row-types/)).
 
 ### Wrong parameters, misspelled columns
 
@@ -143,11 +148,11 @@ conn.execute(SQL[tuple[str | None]]("--sql\nSELECT email FROM users WHERE id = ?
 conn.execute("--sql\nSELECT emial FROM users")
 ```
 
-`?`, `$1`, `%s` and `:name` placeholders are checked on sqlite3, psycopg and
-asyncpg calls ([Parameters](https://jirikuncar.github.io/sqlty/guide/parameters/)).
+`?`, `$1`, `%s` and `:name` placeholders are checked on sqlite3, aiosqlite,
+psycopg and asyncpg calls ([Parameters](https://sqlty.kuncar.dev/guide/parameters/)).
 These are the mistakes coding agents make: every problem is one
 `file:line: [rule] message` line and a non-zero exit code they can act on, and
-the [sqlty skills](https://jirikuncar.github.io/sqlty/recipes/agents/) teach
+the [sqlty skills](https://sqlty.kuncar.dev/recipes/agents/) teach
 them the conventions. In Claude Code, `/plugin install sqlty --marketplace jirikuncar/sqlty`
 installs them.
 
@@ -163,13 +168,13 @@ sqlty strip .                  # undo: back to plain strings
 
 `rewrite` and `strip` only touch the wrapper, never the SQL, so you can adopt
 sqlty one module at a time and back out. New project:
-[Quickstart](https://jirikuncar.github.io/sqlty/quickstart/). Existing codebase:
-[Migration](https://jirikuncar.github.io/sqlty/recipes/migration/), starting
+[Quickstart](https://sqlty.kuncar.dev/quickstart/). Existing codebase:
+[Migration](https://sqlty.kuncar.dev/recipes/migration/), starting
 with `pg_dump --schema-only app > schema.sql`. In the editor:
-[VS Code](https://jirikuncar.github.io/sqlty/recipes/vscode/).
+[VS Code](https://sqlty.kuncar.dev/recipes/vscode/).
 
 Not a fit for ORMs, SQL built at runtime, or runtime validation;
-[Why SQLTy?](https://jirikuncar.github.io/sqlty/motivation/) compares it with
+[Why SQLTy?](https://sqlty.kuncar.dev/motivation/) compares it with
 sqlc, sqlx, PgTyped and others.
 
 ## About
@@ -180,5 +185,5 @@ developed with AI coding agents, mainly Claude Code; every change is reviewed by
 a maintainer (see the
 [AI-assisted contributions](https://github.com/jirikuncar/sqlty/blob/main/CONTRIBUTING.md#ai-assisted-contributions)
 policy). [Contributing](https://github.com/jirikuncar/sqlty/blob/main/CONTRIBUTING.md) ·
-[Credits](https://jirikuncar.github.io/sqlty/credits/) ·
+[Credits](https://sqlty.kuncar.dev/credits/) ·
 MIT [License](https://github.com/jirikuncar/sqlty/blob/main/LICENSE).

{sqlty-0.4.0 → sqlty-0.6.0}/pyproject.toml

@@ -1,7 +1,7 @@
 [project]
 name = "sqlty"
 dynamic = ["version"]
-description = "Type-safe SQL queries for Python"
+description = "Type-safe raw SQL for Python: row and parameter types inferred from your SQL and schema, no ORM or database needed"
 readme = "README.md"
 requires-python = ">=3.14"
 license = "MIT"
@@ -9,11 +9,22 @@ license-files = ["LICENSE"]
 authors = [{ name = "Jiri Kuncar", email = "jiri.kuncar@gmail.com" }]
 keywords = [
     "sql",
-    "type-hints",
-    "mypy",
+    "raw-sql",
     "type-safety",
+    "type-checking",
+    "type-hints",
     "static-analysis",
+    "linter",
+    "mypy",
+    "pyright",
+    "ty",
+    "postgresql",
+    "sqlite",
+    "mysql",
+    "psycopg",
+    "migrations",
     "code-generation",
+    "orm-alternative",
 ]
 classifiers = [
     "Development Status :: 4 - Beta",
@@ -27,6 +38,7 @@ classifiers = [
     "Programming Language :: SQL",
     "Topic :: Software Development :: Code Generators",
     "Topic :: Software Development :: Libraries :: Python Modules",
+    "Topic :: Software Development :: Quality Assurance",
     "Topic :: Database",
     "Typing :: Typed",
 ]
@@ -36,8 +48,8 @@ dependencies = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/jirikuncar/sqlty"
-Documentation = "https://jirikuncar.github.io/sqlty/"
+Homepage = "https://sqlty.kuncar.dev/"
+Documentation = "https://sqlty.kuncar.dev/"
 Repository = "https://github.com/jirikuncar/sqlty"
 Changelog = "https://github.com/jirikuncar/sqlty/releases"
 Issues = "https://github.com/jirikuncar/sqlty/issues"
@@ -45,11 +57,14 @@ Issues = "https://github.com/jirikuncar/sqlty/issues"
 [project.scripts]
 sqlty = "sqlty._cli:main"
 
+[project.entry-points."pygments.lexers"]
+sqlty = "sqlty.lexer:SQLTyLexer"
+
 [project.optional-dependencies]
 psycopg = ["psycopg>=3.2.12"]
 
 [build-system]
-requires = ["maturin>=1.12.1,<2.0"]
+requires = ["maturin>=1.15,<2.0"]
 build-backend = "maturin"
 
 [tool.maturin]
@@ -67,7 +82,7 @@ include = ["src/sqlty_magic.pth", { path = "skills/**/*", format = "sdist" }]
 [dependency-groups]
 dev = [
     "inline-snapshot>=0.15.0",
-    "maturin>=1.12.1,<2.0",
+    "maturin>=1.15,<2.0",
     "mypy>=2.4.0",
     "prek>=0.5.4",
     "pyright>=1.1.414",
@@ -83,11 +98,14 @@ dev = [
     "pydantic[email]>=2.14.1",
     "jsonschema>=4.26.0",
     "pytest-xdist>=3.8.0",
+    "types-pygments>=2.19",
 ]
 cli = ["rich>=15.0.0"]
 # Only the DuckDB type tests need it, and it has no wheel for every Python.
 duckdb = ["duckdb>=1.4.0"]
 psycopg = ["psycopg>=3.2.12"]
+# The aiosqlite calls sqlty checks, run against aiosqlite (tests/test_aiosqlite.py).
+aiosqlite = ["aiosqlite>=0.22.1"]
 fuzz = [
     "hypothesis>=6.140",
 ]
@@ -112,7 +130,7 @@ markers = [
 concurrency = ["multiprocessing"]
 parallel = true
 sigterm = true
-patch = ["subprocess"]
+patch = ["subprocess", "_exit"]
 omit = ["tests/*", "examples/*"]
 
 [tool.coverage.paths]