iddqueue 0.13.0rc1__tar.gz → 0.13.0rc2__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (26) hide show
  1. iddqueue-0.13.0rc2/PKG-INFO +180 -0
  2. iddqueue-0.13.0rc2/README.md +159 -0
  3. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/cli.py +0 -5
  4. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/pyproject.toml +4 -2
  5. iddqueue-0.13.0rc1/PKG-INFO +0 -730
  6. iddqueue-0.13.0rc1/README.md +0 -709
  7. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/LICENSE +0 -0
  8. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/__init__.py +0 -0
  9. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/broker.py +0 -0
  10. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/cancellation.py +0 -0
  11. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/cancellation.sql +0 -0
  12. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/control.py +0 -0
  13. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/control.sql +0 -0
  14. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/coordination.sql +0 -0
  15. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/deduplication.sql +0 -0
  16. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/failures.py +0 -0
  17. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/history.py +0 -0
  18. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/history.sql +0 -0
  19. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/metrics.py +0 -0
  20. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/rate_limits.py +0 -0
  21. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/results.py +0 -0
  22. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/scheduler.py +0 -0
  23. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/scheduler.sql +0 -0
  24. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/schema.py +0 -0
  25. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/schema.sql +0 -0
  26. {iddqueue-0.13.0rc1 → iddqueue-0.13.0rc2}/iddqueue/utils.py +0 -0
@@ -0,0 +1,180 @@
1
+ Metadata-Version: 2.4
2
+ Name: iddqueue
3
+ Version: 0.13.0rc2
4
+ Summary: Postgres Broker for Dramatiq Task Queue
5
+ Keywords: postgres,task queue,dramatiq
6
+ Author: Étienne BERSAC
7
+ License-Expression: PostgreSQL
8
+ License-File: LICENSE
9
+ Requires-Dist: dramatiq>=2.2.1,<3
10
+ Requires-Dist: psycopg>=3.3.6,<4
11
+ Requires-Dist: psycopg-pool>=3.3.3,<4
12
+ Requires-Dist: tenacity>=9,<10
13
+ Requires-Dist: psycopg[binary]>=3.3.6,<4 ; extra == 'binary'
14
+ Requires-Dist: dramatiq[prometheus]>=2.2.1,<3 ; extra == 'monitoring'
15
+ Requires-Python: >=3.10, <4
16
+ Project-URL: Repository, https://github.com/wa-pis/iddqueue
17
+ Project-URL: Issues, https://github.com/wa-pis/iddqueue/issues
18
+ Provides-Extra: binary
19
+ Provides-Extra: monitoring
20
+ Description-Content-Type: text/markdown
21
+
22
+ # IDDQueue
23
+
24
+ [Documentation](https://wa-pis.github.io/iddqueue/) · [Step-by-step setup](https://wa-pis.github.io/iddqueue/walkthrough/)
25
+
26
+ A PostgreSQL broker and Results backend for [Dramatiq](https://dramatiq.io/),
27
+ built on synchronous Psycopg 3. Tasks, results and coordination live in PostgreSQL;
28
+ no Redis or ORM is required by IDDQueue.
29
+
30
+ **Current release: [0.13.0rc2](https://pypi.org/project/iddqueue/0.13.0rc2/)** —
31
+ a release candidate for evaluation. [GitHub assets](https://github.com/wa-pis/iddqueue/releases/tag/v0.13.0rc2)
32
+ include the wheel, sdist and SHA256 checksums.
33
+
34
+ IDDQueue is a fork of [DALIBO's dramatiq-pg](https://gitlab.com/dalibo/dramatiq-pg)
35
+ ([original package](https://pypi.org/project/dramatiq-pg/)). It preserves the
36
+ PostgreSQL license and original contributor credits.
37
+
38
+ ## What it provides
39
+
40
+ - Durable JSONB task/results storage, delayed tasks and crash recovery.
41
+ - Transactional publication alongside business writes; atomic batches and deduplication.
42
+ - PostgreSQL rate limiters, barriers and Dramatiq group callbacks.
43
+ - Pause/resume, cooperative cancellation, failed-task inspection/retry and attempt history.
44
+ - Fixed-interval scheduling and optional Prometheus queue metrics.
45
+ - Schema/prefix isolation and a [tested FastAPI example](docs/fastapi.md).
46
+
47
+ Delivery is **at least once**: actors and callbacks must be idempotent.
48
+ LISTEN/NOTIFY carries message IDs as wakeup hints; consumers claim authoritative
49
+ SQL rows with session advisory locks. See [behavior and limits](docs/user-guide.md).
50
+
51
+ ## Install
52
+
53
+ Requires Python 3.10+, Dramatiq 2.2.1+ and Psycopg 3.3.6+.
54
+ CI tests Python **3.10 / 3.13 / 3.14** with PostgreSQL **14 / 18**.
55
+ See [compatibility and API stability](SUPPORT.md).
56
+
57
+ ```sh
58
+ uv venv
59
+ uv pip install "iddqueue[binary]==0.13.0rc2"
60
+ ```
61
+
62
+ The `binary` extra supplies libpq. Base installs require system libpq;
63
+ `[binary,monitoring]` also enables Prometheus support.
64
+
65
+ **Migrating from dramatiq-pg?** Follow the [migration guide](docs/migration.md)
66
+ before changing imports, pools or database storage. Stop all participants,
67
+ back up data, run the upgrade and restart consistently. Fresh initialization
68
+ and an existing-storage upgrade are different operations.
69
+
70
+ ## Quickstart
71
+
72
+ Configure PostgreSQL using `PGHOST`, `PGPORT`, `PGUSER`, `PGDATABASE` and your
73
+ normal credential mechanism. Initialize fresh storage:
74
+
75
+ ```sh
76
+ uv run --no-sync iddqueue init
77
+ ```
78
+
79
+ For existing storage, use `iddqueue upgrade` after following the migration guide.
80
+ Both commands manage the complete feature schema.
81
+
82
+ Save as `tasks.py`:
83
+
84
+ ```python
85
+ import dramatiq
86
+ from iddqueue import PostgresBroker
87
+
88
+ broker = PostgresBroker()
89
+ dramatiq.set_broker(broker)
90
+
91
+ @dramatiq.actor(broker=broker, store_results=True)
92
+ def add(left: int, right: int):
93
+ return left + right
94
+ ```
95
+
96
+ Start a separate worker from the same directory/environment:
97
+
98
+ ```sh
99
+ uv run --no-sync dramatiq --use-spawn --processes=1 --threads=1 tasks
100
+ ```
101
+
102
+ In another terminal, publish and read the result:
103
+
104
+ ```sh
105
+ uv run --no-sync python - <<'PY'
106
+ from tasks import add, broker
107
+
108
+ try:
109
+ message = add.send(2, 3)
110
+ print(message.message_id)
111
+ print(message.get_result(backend=broker.backend, block=True, timeout=10000))
112
+ finally:
113
+ broker.close()
114
+ PY
115
+ ```
116
+
117
+ The result is `5`; timeouts are milliseconds. Each process creates its own pool.
118
+ Close broker-owned pools on shutdown; callers close pools they supply.
119
+
120
+ ## Guides and examples
121
+
122
+ - [Documentation index](docs/index.md), [user guide](docs/user-guide.md), [API](docs/api.md).
123
+ - [Detailed recipes](docs/recipes.md): transactions, middleware, controls, metrics and schedules.
124
+ - [FastAPI](docs/fastapi.md): lifespan, async endpoint thread offload and separate worker.
125
+ - [Deployment and retention](docs/deployment-guide.md), [why PostgreSQL](docs/why.md).
126
+ - [RC notes](docs/rc-0.13.0rc2.md), [changelog](CHANGELOG.md), [release checks](docs/release.md).
127
+
128
+ The broker and result APIs are synchronous. Async actors use Dramatiq's AsyncIO
129
+ middleware; FastAPI async endpoints offload publication to a thread.
130
+ Transactional enqueue does not accept a Psycopg AsyncConnection.
131
+
132
+ Session-bound locks/listeners require persistent database sessions; PgBouncer
133
+ transaction pooling is unsuitable. Namespace separation is not access control.
134
+ The legacy [django-dramatiq-pg](https://github.com/uptick/django-dramatiq-pg/)
135
+ integration has been archived since September 3, 2024; IDDQueue compatibility
136
+ is unverified. No tested Django integration is currently provided.
137
+
138
+ ## Compared with dramatiq-pg
139
+
140
+ Baseline: [dramatiq-pg 0.12.0](https://pypi.org/project/dramatiq-pg/0.12.0/),
141
+ compared with the published IDDQueue 0.13.0rc2 prerelease. This describes the published version, not every
142
+ future upstream revision. Both projects provide a PostgreSQL Dramatiq broker.
143
+
144
+ | Area | dramatiq-pg 0.12.0 | IDDQueue 0.13.0rc2 / practical benefit |
145
+ | --- | --- | --- |
146
+ | Core storage and delivery | JSONB tasks/results, delayed tasks, LISTEN/NOTIFY, advisory locks, recovery and maintenance CLI | Preserved; at-least-once delivery still requires idempotent actors |
147
+ | Runtime | Python >=3.6,<4; Dramatiq >=1.5,<2; Psycopg 2 | Python >=3.10,<4; Dramatiq >=2.2.1,<3; synchronous Psycopg 3 and psycopg-pool |
148
+ | Pool lifecycle | Psycopg 2 pools | Lazy owned pools, explicit close, caller-owned pool support |
149
+ | Transactional publication | Regular enqueue | Caller-owned transaction API: commit business data and tasks together |
150
+ | Coordination | No PostgreSQL rate-limit/barrier backend | PostgreSQL rate limits, durable barriers and standard GroupCallbacks without Redis |
151
+ | Task operations | stats, purge, recover, flush | Failed-task inspection/targeted retry, pause/resume, cooperative cancellation and opt-in attempt history |
152
+ | Publication controls | Single-message enqueue | Deduplication keys/TTL and atomic batches of up to 1000; deduplication is not exactly-once execution |
153
+ | Scheduling | Per-message delay | Also a multi-process fixed-interval scheduler; no cron/calendar expressions |
154
+ | Observability | Basic CLI statistics | Ready/scheduled backlog, task age and optional Prometheus collector |
155
+ | Storage namespaces | Configurable schema/table prefix; shared channel/lock domains | Instance-specific queries and schema/prefix-specific channels/locks; storage separation is not access control |
156
+ | Dramatiq integration | Broker/results implementation | Verified pipelines, groups, AsyncIO and standard middleware; these are Dramatiq features, not a replacement orchestration engine |
157
+ | Compatibility evidence | Historical upstream tests | CI on Python 3.10/3.13/3.14 × PostgreSQL 14/18, functional tests and installed-wheel checks |
158
+
159
+ See [migration from dramatiq-pg](docs/migration.md) for dependency, pool,
160
+ import, CLI and database changes, including backup and rollback. No throughput
161
+ advantage is claimed here. The 0.13.0rc2 prerelease is available on PyPI; the legacy Django
162
+ integration is archived and has not been verified with IDDQueue.
163
+
164
+ ## Development and support
165
+
166
+ Use [CONTRIBUTING](CONTRIBUTING.md) for locked uv setup and the full release gate.
167
+ Functional tests require a dedicated PostgreSQL instance: they terminate sessions
168
+ and crash/restart workers. Project planning and evidence live in
169
+ [OpenSpec](openspec/roadmap.md). Report reproducible issues on
170
+ [GitHub](https://github.com/wa-pis/iddqueue/issues).
171
+
172
+ ## License and credits
173
+
174
+ Released under the [PostgreSQL license](LICENSE), preserving
175
+ `Copyright (c) 2019, DALIBO` and the original author Étienne BERSAC.
176
+
177
+ Thanks to upstream contributors Andy Freeland, Curtis Maloney (Django support),
178
+ Federico Caselli, Giuseppe Papallo and Rafal Kwasny. The historical upstream logo
179
+ was created by [Damien CAZEILS](http://www.damiencazeils.com/).
180
+ [Original changelog](docs/changelog.rst) remains available as historical context.
@@ -0,0 +1,159 @@
1
+ # IDDQueue
2
+
3
+ [Documentation](https://wa-pis.github.io/iddqueue/) · [Step-by-step setup](https://wa-pis.github.io/iddqueue/walkthrough/)
4
+
5
+ A PostgreSQL broker and Results backend for [Dramatiq](https://dramatiq.io/),
6
+ built on synchronous Psycopg 3. Tasks, results and coordination live in PostgreSQL;
7
+ no Redis or ORM is required by IDDQueue.
8
+
9
+ **Current release: [0.13.0rc2](https://pypi.org/project/iddqueue/0.13.0rc2/)** —
10
+ a release candidate for evaluation. [GitHub assets](https://github.com/wa-pis/iddqueue/releases/tag/v0.13.0rc2)
11
+ include the wheel, sdist and SHA256 checksums.
12
+
13
+ IDDQueue is a fork of [DALIBO's dramatiq-pg](https://gitlab.com/dalibo/dramatiq-pg)
14
+ ([original package](https://pypi.org/project/dramatiq-pg/)). It preserves the
15
+ PostgreSQL license and original contributor credits.
16
+
17
+ ## What it provides
18
+
19
+ - Durable JSONB task/results storage, delayed tasks and crash recovery.
20
+ - Transactional publication alongside business writes; atomic batches and deduplication.
21
+ - PostgreSQL rate limiters, barriers and Dramatiq group callbacks.
22
+ - Pause/resume, cooperative cancellation, failed-task inspection/retry and attempt history.
23
+ - Fixed-interval scheduling and optional Prometheus queue metrics.
24
+ - Schema/prefix isolation and a [tested FastAPI example](docs/fastapi.md).
25
+
26
+ Delivery is **at least once**: actors and callbacks must be idempotent.
27
+ LISTEN/NOTIFY carries message IDs as wakeup hints; consumers claim authoritative
28
+ SQL rows with session advisory locks. See [behavior and limits](docs/user-guide.md).
29
+
30
+ ## Install
31
+
32
+ Requires Python 3.10+, Dramatiq 2.2.1+ and Psycopg 3.3.6+.
33
+ CI tests Python **3.10 / 3.13 / 3.14** with PostgreSQL **14 / 18**.
34
+ See [compatibility and API stability](SUPPORT.md).
35
+
36
+ ```sh
37
+ uv venv
38
+ uv pip install "iddqueue[binary]==0.13.0rc2"
39
+ ```
40
+
41
+ The `binary` extra supplies libpq. Base installs require system libpq;
42
+ `[binary,monitoring]` also enables Prometheus support.
43
+
44
+ **Migrating from dramatiq-pg?** Follow the [migration guide](docs/migration.md)
45
+ before changing imports, pools or database storage. Stop all participants,
46
+ back up data, run the upgrade and restart consistently. Fresh initialization
47
+ and an existing-storage upgrade are different operations.
48
+
49
+ ## Quickstart
50
+
51
+ Configure PostgreSQL using `PGHOST`, `PGPORT`, `PGUSER`, `PGDATABASE` and your
52
+ normal credential mechanism. Initialize fresh storage:
53
+
54
+ ```sh
55
+ uv run --no-sync iddqueue init
56
+ ```
57
+
58
+ For existing storage, use `iddqueue upgrade` after following the migration guide.
59
+ Both commands manage the complete feature schema.
60
+
61
+ Save as `tasks.py`:
62
+
63
+ ```python
64
+ import dramatiq
65
+ from iddqueue import PostgresBroker
66
+
67
+ broker = PostgresBroker()
68
+ dramatiq.set_broker(broker)
69
+
70
+ @dramatiq.actor(broker=broker, store_results=True)
71
+ def add(left: int, right: int):
72
+ return left + right
73
+ ```
74
+
75
+ Start a separate worker from the same directory/environment:
76
+
77
+ ```sh
78
+ uv run --no-sync dramatiq --use-spawn --processes=1 --threads=1 tasks
79
+ ```
80
+
81
+ In another terminal, publish and read the result:
82
+
83
+ ```sh
84
+ uv run --no-sync python - <<'PY'
85
+ from tasks import add, broker
86
+
87
+ try:
88
+ message = add.send(2, 3)
89
+ print(message.message_id)
90
+ print(message.get_result(backend=broker.backend, block=True, timeout=10000))
91
+ finally:
92
+ broker.close()
93
+ PY
94
+ ```
95
+
96
+ The result is `5`; timeouts are milliseconds. Each process creates its own pool.
97
+ Close broker-owned pools on shutdown; callers close pools they supply.
98
+
99
+ ## Guides and examples
100
+
101
+ - [Documentation index](docs/index.md), [user guide](docs/user-guide.md), [API](docs/api.md).
102
+ - [Detailed recipes](docs/recipes.md): transactions, middleware, controls, metrics and schedules.
103
+ - [FastAPI](docs/fastapi.md): lifespan, async endpoint thread offload and separate worker.
104
+ - [Deployment and retention](docs/deployment-guide.md), [why PostgreSQL](docs/why.md).
105
+ - [RC notes](docs/rc-0.13.0rc2.md), [changelog](CHANGELOG.md), [release checks](docs/release.md).
106
+
107
+ The broker and result APIs are synchronous. Async actors use Dramatiq's AsyncIO
108
+ middleware; FastAPI async endpoints offload publication to a thread.
109
+ Transactional enqueue does not accept a Psycopg AsyncConnection.
110
+
111
+ Session-bound locks/listeners require persistent database sessions; PgBouncer
112
+ transaction pooling is unsuitable. Namespace separation is not access control.
113
+ The legacy [django-dramatiq-pg](https://github.com/uptick/django-dramatiq-pg/)
114
+ integration has been archived since September 3, 2024; IDDQueue compatibility
115
+ is unverified. No tested Django integration is currently provided.
116
+
117
+ ## Compared with dramatiq-pg
118
+
119
+ Baseline: [dramatiq-pg 0.12.0](https://pypi.org/project/dramatiq-pg/0.12.0/),
120
+ compared with the published IDDQueue 0.13.0rc2 prerelease. This describes the published version, not every
121
+ future upstream revision. Both projects provide a PostgreSQL Dramatiq broker.
122
+
123
+ | Area | dramatiq-pg 0.12.0 | IDDQueue 0.13.0rc2 / practical benefit |
124
+ | --- | --- | --- |
125
+ | Core storage and delivery | JSONB tasks/results, delayed tasks, LISTEN/NOTIFY, advisory locks, recovery and maintenance CLI | Preserved; at-least-once delivery still requires idempotent actors |
126
+ | Runtime | Python >=3.6,<4; Dramatiq >=1.5,<2; Psycopg 2 | Python >=3.10,<4; Dramatiq >=2.2.1,<3; synchronous Psycopg 3 and psycopg-pool |
127
+ | Pool lifecycle | Psycopg 2 pools | Lazy owned pools, explicit close, caller-owned pool support |
128
+ | Transactional publication | Regular enqueue | Caller-owned transaction API: commit business data and tasks together |
129
+ | Coordination | No PostgreSQL rate-limit/barrier backend | PostgreSQL rate limits, durable barriers and standard GroupCallbacks without Redis |
130
+ | Task operations | stats, purge, recover, flush | Failed-task inspection/targeted retry, pause/resume, cooperative cancellation and opt-in attempt history |
131
+ | Publication controls | Single-message enqueue | Deduplication keys/TTL and atomic batches of up to 1000; deduplication is not exactly-once execution |
132
+ | Scheduling | Per-message delay | Also a multi-process fixed-interval scheduler; no cron/calendar expressions |
133
+ | Observability | Basic CLI statistics | Ready/scheduled backlog, task age and optional Prometheus collector |
134
+ | Storage namespaces | Configurable schema/table prefix; shared channel/lock domains | Instance-specific queries and schema/prefix-specific channels/locks; storage separation is not access control |
135
+ | Dramatiq integration | Broker/results implementation | Verified pipelines, groups, AsyncIO and standard middleware; these are Dramatiq features, not a replacement orchestration engine |
136
+ | Compatibility evidence | Historical upstream tests | CI on Python 3.10/3.13/3.14 × PostgreSQL 14/18, functional tests and installed-wheel checks |
137
+
138
+ See [migration from dramatiq-pg](docs/migration.md) for dependency, pool,
139
+ import, CLI and database changes, including backup and rollback. No throughput
140
+ advantage is claimed here. The 0.13.0rc2 prerelease is available on PyPI; the legacy Django
141
+ integration is archived and has not been verified with IDDQueue.
142
+
143
+ ## Development and support
144
+
145
+ Use [CONTRIBUTING](CONTRIBUTING.md) for locked uv setup and the full release gate.
146
+ Functional tests require a dedicated PostgreSQL instance: they terminate sessions
147
+ and crash/restart workers. Project planning and evidence live in
148
+ [OpenSpec](openspec/roadmap.md). Report reproducible issues on
149
+ [GitHub](https://github.com/wa-pis/iddqueue/issues).
150
+
151
+ ## License and credits
152
+
153
+ Released under the [PostgreSQL license](LICENSE), preserving
154
+ `Copyright (c) 2019, DALIBO` and the original author Étienne BERSAC.
155
+
156
+ Thanks to upstream contributors Andy Freeland, Curtis Maloney (Django support),
157
+ Federico Caselli, Giuseppe Papallo and Rafal Kwasny. The historical upstream logo
158
+ was created by [Damien CAZEILS](http://www.damiencazeils.com/).
159
+ [Original changelog](docs/changelog.rst) remains available as historical context.
@@ -114,7 +114,6 @@ def make_argument_parser():
114
114
  "-d",
115
115
  "--dsn",
116
116
  "--connstring",
117
- action="store",
118
117
  dest="url",
119
118
  default="",
120
119
  metavar="CONNSTRING",
@@ -122,8 +121,6 @@ def make_argument_parser():
122
121
  )
123
122
  parser.add_argument(
124
123
  "--schemaname",
125
- action="store",
126
- dest="schemaname",
127
124
  default="dramatiq",
128
125
  metavar="SCHEMA",
129
126
  help=(
@@ -132,8 +129,6 @@ def make_argument_parser():
132
129
  )
133
130
  parser.add_argument(
134
131
  "--prefix",
135
- action="store",
136
- dest="prefix",
137
132
  default="",
138
133
  metavar="PREFIX",
139
134
  help='Prefix for table name for message. Default is "%(default)s".',
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "iddqueue"
3
- version = "0.13.0rc1"
3
+ version = "0.13.0rc2"
4
4
  description = "Postgres Broker for Dramatiq Task Queue"
5
5
  authors = [{name = "Étienne BERSAC"}]
6
6
  license = "PostgreSQL"
@@ -29,12 +29,14 @@ iddqueue = "iddqueue.cli:entrypoint"
29
29
  [dependency-groups]
30
30
  dev = [
31
31
  "pytest>=8", "pytest-timeout>=2", "pytest-mock>=3",
32
- "dramatiq[watch]>=2.2.1,<3", "psycopg[binary]>=3.3.6,<4",
32
+ "psycopg[binary]>=3.3.6,<4",
33
33
  "docutils>=0.21", "pygments>=2.20", "ruff>=0.9",
34
34
  ]
35
35
 
36
36
  fastapi-example = ["fastapi>=0.115,<1", "httpx>=0.28,<1", "uvicorn>=0.34,<1"]
37
37
 
38
+ docs = ["mkdocs>=1.6.1,<2"]
39
+
38
40
  [build-system]
39
41
  requires = ["uv_build>=0.11.23,<0.12"]
40
42
  build-backend = "uv_build"