pydantic-linq
C# LINQ for Python. It has every System.Linq and System.Linq.Async operator, is fully typed, and works with Pydantic models.
Documentation: https://codejunction.github.io/pydantic-linq/
pip install pydantic-linq
from pydantic import BaseModel
import pydantic_linq # adds LINQ operators to list / tuple / set / frozenset
class Row(BaseModel):
id: int
tag: str
rows = [Row(id=1, tag="a"), Row(id=2, tag="b"), Row(id=3, tag="a")]
rows.where(lambda r: r.tag == "a").select(lambda r: r.id).to_list() # [1, 3]
rows.group_by(lambda r: r.tag).select(lambda g: (g.key, g.count())).to_list() # [('a', 2), ('b', 1)]
rows.order_by_descending(lambda r: r.id).then_by(lambda r: r.tag).first()
Async
AsyncEnumerable covers System.Linq.Async. It wraps any sync or async iterable. Sequence operators are deferred, and terminal operators are awaited:
async def load_age(r: Row) -> int: ...
ages = await rows.to_async_enumerable().where(lambda r: r.id > 1).select(load_age).to_list()
A selector or predicate can be a plain function or an async def, so there are no separate *Await overloads. Terminal operators keep the sync names (to_list, first, count) and are awaited. The C# Async suffix is dropped.
Entity Framework (SQLModel)
pydantic_linq.orm is Entity Framework Core for SQLModel. The same LINQ operators build SQL, and the EF features are there: DbContext, include / then_include, as_no_tracking, execute_update / execute_delete, from_sql, and a *_async twin of every terminal operator.
pip install "pydantic-linq[sqlmodel]"
from sqlmodel import create_engine
from sqlalchemy.ext.asyncio import create_async_engine
from pydantic_linq.orm import DbContext
with DbContext(create_engine("sqlite:///app.db")) as db:
db.set(Hero).where(lambda h: (h.age > 30) & (h.team_id == 1)).order_by(lambda h: h.name).take(10).to_list()
# SELECT ... FROM hero WHERE hero.age > 30 AND hero.team_id = 1 ORDER BY hero.name LIMIT 10
db.set(Hero).group_by(lambda h: h.team_id).select(lambda g: (g.key, g.count(), g.average(lambda h: h.age))).to_list()
# SELECT hero.team_id, count(*), avg(hero.age) FROM hero GROUP BY hero.team_id
db.set(Hero).include(lambda h: h.team).first(lambda h: h.name == "Tony")
db.set(Hero).where(lambda h: h.age > 100).execute_update(lambda h: {h.age: h.age + 1})
async with DbContext(create_async_engine("sqlite+aiosqlite:///app.db")) as db:
adults = await db.set(Hero).where(lambda h: h.age >= 18).to_list_async()
A lambda is called with the model class, so it builds a SQLAlchemy expression. Combine conditions with &, | and ~, not and, or and not. A select SQL can't express runs in memory, as EF's client projection does, and so does every operator EF doesn't translate. The Entity Framework guide maps each EF Core feature.
Conventions
- Method names are the C# names in snake_case:
OrderByDescendingbecomesorder_by_descending.Exceptbecomesexcept_, becauseexceptis a Python keyword. The operator map lists every operator. - Operators that return a sequence are deferred and can be enumerated again, as in .NET.
- Equality uses value semantics (
==). Non-frozen (unhashable) pydantic models work indistinct,unionand the other set operators. cast(Model)validates each element with a pydanticTypeAdapter, so dicts become models.of_type(Model)filters withisinstance.Enumerable[Model]can be a pydantic field type. It validates likelist[Model]and serializes as a list.group_byyieldsGroupingobjects. Each is itself anEnumerablewith a.key.- C#
KeyValuePairbecomes a(key, value)tuple.IComparerbecomes acmp(a, b) -> intfunction. A C#RangeorIndex(for example^1) becomes a slice or a negative int. - Lambda overloads that take an index (
Select((x, i) => ...)) map to.index(), followed by the operator. - Empty-sequence errors raise
InvalidOperationError, which subclassesValueError.
Builtin patching
Importing the package uses forbiddenfruit to patch list, tuple, set and frozenset. A builtin method that already exists keeps its Python meaning, for example list.count(x) and list.reverse(). To get the LINQ version, use rows.as_enumerable().count(). Type checkers do not see the patched methods. Where you need static types, use Enumerable(rows). To remove the patches, call pydantic_linq.uninstall().
Examples
examples/ runs from simple to complex: 01_basics through 07_sales_report, an end-to-end report pipeline, then 08_entity_framework and 09_entity_framework_async for database queries. Run any of them with uv run python examples/01_basics.py.
Layout
src/pydantic_linq/
core/ errors, value-equality set, group and sort helpers (no internal deps)
sync/
base.py EnumerableBase, deferred execution
operators/ one mixin per LINQ category: filtering, projection, partitioning, sets, sorting, ...
enumerable.py Enumerable = all mixins
ordered.py OrderedEnumerable (then_by)
grouping.py Grouping (an Enumerable with .key), Lookup
aio/ AsyncEnumerable, same layout as sync/
integrations/ pydantic field schema, builtin patching
orm/ Entity Framework over SQLModel: Queryable, DbContext (optional extra)
docs/ documentation site (MkDocs); the API reference is generated from the docstrings
Contributing
Every code change also updates CHANGELOG.md (under [Unreleased]) and the docs in docs/. See CLAUDE.md for the checks and the release steps.
Changelog
See CHANGELOG.md.
Metadata
Release files for pydantic-linq 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pydantic_linq-0.1.1.tar.gz | 119.1 kB | With provenance | Details for pydantic_linq-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydantic_linq-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for pydantic_linq-0.1.1-py3-none-any.whl |
Total release size: 172.1 kB
Release files / pydantic_linq-0.1.1.tar.gz
| Download URL | pydantic_linq-0.1.1.tar.gz |
|---|---|
| Size | 119.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43fe6163332ed4785312b87571562548d47637062d44021857f358c851b7457b
|
|
BLAKE2b-256 checksum How to use checksums |
bcc073a4446ded9ac26a84278844f3ff84b257df00f1e37d357e1b6d91168457
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / pydantic_linq-0.1.1-py3-none-any.whl
| Download URL | pydantic_linq-0.1.1-py3-none-any.whl |
|---|---|
| Size | 53.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
62036155929a14b10e8deee29d285805bfe1cb931481cce6be9be7fc12b42139
|
|
BLAKE2b-256 checksum How to use checksums |
7448da0b6607268781f7c52bf96669c61233dcb4fc68529ce5a89543eae113de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logSecurity for pydantic-linq 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pydantic_linq-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.