django-harel 0.1.0__tar.gz

django_harel-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+.venv/
+docs/_build/
+*.db
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+bench/logs/
+.vscode/

django_harel-0.1.0/CHANGELOG.md

@@ -0,0 +1,42 @@
+# Changelog
+
+All notable changes to django-harel. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and versions follow
+[Semantic Versioning](https://semver.org/) (pre-1.0: a minor version may break the API).
+
+## 0.1.0 - 2026-10-31
+
+The first release. It requires Python 3.11+, Django 5.2+ and harel 0.10+.
+
+### Added
+
+- **Storage on Django's database.** `DjangoStore` and `DjangoTransport` implement harel's
+  `ExecutionStore` and `Transport` protocols over Django's own connection, so an execution's
+  state, queue and timers join the caller's transaction. They pass harel's contract suites
+  (`harel.testing`).
+- **SQLite, PostgreSQL and MySQL/MariaDB.** One migration creates harel's schema version 6. On
+  SQLite and PostgreSQL the tables are harel's own, so harel's native backends and tools can
+  read them.
+- **`ExecutionField`.** It ties a machine to a model, as an attribute named after the machine:
+  `article.publishing.send("Submit")`, `.state`, `.process(...)` in the request. With
+  `autostart=True`, the execution starts with the row.
+- **Runners.** `distributed_runner()` queues events for a worker. `durable_runner()` runs them in
+  the request. `definitions()` loads the machines in `DJANGO_HAREL["MACHINES"]`.
+- **`manage.py harel_worker`.** Each event runs in one transaction: its actions' writes, the
+  machine's step and the acknowledgement commit together.
+  - `--machines` dedicates a worker to some machines.
+  - At startup the worker publishes the machine versions it runs.
+  - It records a heartbeat every `HEARTBEAT` seconds and removes it when it stops.
+- **Signals.** `step_committed`, `execution_finished` and `execution_failed` are sent once the
+  step's transaction has committed.
+- **The admin.**
+  - **Executions**: each execution's diagram with its active states, its tree of regions and
+    children, what it waits for, and its timeline.
+  - **Actions** on the executions list: suspend, resume, cancel, terminate, purge, and redrive
+    failed executions at a chosen state.
+  - **Machines**: every machine with its version, diagram and top-level executions; counts by
+    status; overdue timers; the queue by machine; and every worker's heartbeat. It flags work
+    no live worker claims, and a gone worker can be forgotten.
+- **Testing helpers.** `ALL_TABLES`, to empty harel's tables between `TransactionTestCase` tests.
+- **An example app** (`example/`): articles and orders, with a REST API, a worker and demo data,
+  on PostgreSQL with `docker compose up`.

django_harel-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work, excluding
+          those notices that do not pertain to any part of the Derivative
+          Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one of
+          the following places: within a NOTICE text file distributed as
+          part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and do
+          not modify the License. You may add Your own attribution notices
+          within Derivative Works that You distribute, alongside or as an
+          addendum to the NOTICE text from the Work, provided that such
+          additional attribution notices cannot be construed as modifying
+          the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Alberto Casado
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

django_harel-0.1.0/PKG-INFO

@@ -0,0 +1,156 @@
+Metadata-Version: 2.5
+Name: django-harel
+Version: 0.1.0
+Summary: Django integration for harel statecharts — a Celery alternative for state-machine-shaped work
+Project-URL: Homepage, https://github.com/acasadom/django-harel
+Project-URL: Repository, https://github.com/acasadom/django-harel
+Project-URL: Issues, https://github.com/acasadom/django-harel/issues
+Author: Alberto Casado
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: celery,django,durable-execution,state-machine,statechart,workflow
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Framework :: Django :: 6.0
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: <4,>=3.11
+Requires-Dist: django>=5.2
+Requires-Dist: harel>=0.10.0
+Description-Content-Type: text/markdown
+
+# django-harel
+
+*Django integration for harel statecharts — a Celery alternative for state-machine-shaped work.*
+
+[![CI](https://github.com/acasadom/django-harel/actions/workflows/ci.yml/badge.svg)](https://github.com/acasadom/django-harel/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/acasadom/django-harel/blob/main/LICENSE)
+![Python](https://img.shields.io/badge/python-3.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)
+
+**django-harel** runs [harel](https://github.com/acasadom/harel) statecharts on Django's
+database. You write a process as a `.stm` machine and its actions as plain functions that use
+the ORM. Its state, its queue and its timers are rows in your database, next to your models.
+It works with SQLite, PostgreSQL and MySQL, and needs no other infrastructure.
+
+Requires Python 3.11+, Django 5.2+ and harel 0.10+. Alpha: the API may still change.
+
+```
+event Submit  {}
+event Approve {}
+event Reject  { note: string }
+
+machine publishing {
+  context { article_id: int }
+
+  initial Draft
+
+  state Draft    {}
+  state InReview { on enter articles.actions.on_in_review }
+  state Approved {}
+
+  final Published success { on enter articles.actions.on_published }
+  final Rejected  failure { on enter articles.actions.on_rejected }
+
+  from Draft    to InReview on Submit
+  from InReview to Approved on Approve
+  from Approved to Published
+  from InReview to Rejected on Reject
+}
+```
+
+## Two ways to run a machine
+
+**In the background**, like Celery, but with the coordination in the machine rather than in
+chained tasks and status fields. The request records the event and answers at once. A worker
+runs it. Waiting days for a webhook, retrying with back-off, timing out, fanning out and
+joining are all part of the machine. A machine waiting for its next event is just a row.
+
+**In the request**, for flows the user drives step by step: wizards, checkouts. The request
+runs the event to the end and renders the new state. There is no queue and no worker.
+
+## Transactions
+
+Everything goes through the connection Django already has, so it joins your transactions:
+
+```python
+class Article(models.Model):
+    ...
+    publishing = ExecutionField("publishing", autostart=True)
+
+
+with transaction.atomic():
+    article = Article.objects.create(...)   # its publishing execution starts with it
+```
+
+If the block rolls back, the execution and its queued `Start` roll back with the article. No
+worker ever runs a workflow for a row that doesn't exist, and you never need
+`transaction.on_commit()`.
+
+On the worker, each event is a transaction too: what its actions write, the machine's step and
+the acknowledgement commit together. A worker that dies halfway leaves nothing behind.
+
+## Install
+
+```bash
+pip install django-harel
+```
+
+```python
+INSTALLED_APPS = [..., "django_harel"]
+
+DJANGO_HAREL = {
+    "MACHINES": {"publishing": "articles/machines/publishing.stm"},
+}
+```
+
+```bash
+python manage.py migrate
+python manage.py harel_worker
+```
+
+## Use
+
+```python
+article.publishing.send("Submit")             # background: queued, the worker runs it
+article.publishing.state                      # "InReview"
+
+order.checkout.process("Pay", token=token)  # in the request: runs now, in this transaction
+```
+
+`ExecutionField` ties a machine to a model; the runners underneath (`distributed_runner()`,
+`durable_runner()`) work for executions that don't belong to a row.
+
+The Django admin's **Machines** catalog lists every machine: its diagram, what it invokes, its
+top-level executions, and their counts by status. It also shows the queue by machine and every
+worker's heartbeat. It flags work no live worker claims, a timer nothing is firing, and a worker
+that is gone. From the executions list you can suspend, resume, cancel, terminate, redrive or
+purge them.
+
+Signals (`step_committed`, `execution_finished`, `execution_failed`) tell your code about every
+step, once its transaction has committed.
+
+## Example
+
+[`example/`](https://github.com/acasadom/django-harel/tree/main/example) is a Django app with
+a REST API (django-ninja) and a worker, on PostgreSQL with `docker compose up`. It has two machines:
+
+- **articles**: the publishing workflow above, the one the tutorial builds.
+- **orders**: shipping and billing in parallel regions, one parcel per item (a fan-out),
+  payment timers, and a refused card to redrive from the admin.
+
+See [`example/README.md`](https://github.com/acasadom/django-harel/blob/main/example/README.md).
+
+## Documentation
+
+[acasadom.github.io/django-harel](https://acasadom.github.io/django-harel/)
+
+## License
+
+Apache 2.0

django_harel-0.1.0/README.md

@@ -0,0 +1,128 @@
+# django-harel
+
+*Django integration for harel statecharts — a Celery alternative for state-machine-shaped work.*
+
+[![CI](https://github.com/acasadom/django-harel/actions/workflows/ci.yml/badge.svg)](https://github.com/acasadom/django-harel/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/acasadom/django-harel/blob/main/LICENSE)
+![Python](https://img.shields.io/badge/python-3.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-blue)
+
+**django-harel** runs [harel](https://github.com/acasadom/harel) statecharts on Django's
+database. You write a process as a `.stm` machine and its actions as plain functions that use
+the ORM. Its state, its queue and its timers are rows in your database, next to your models.
+It works with SQLite, PostgreSQL and MySQL, and needs no other infrastructure.
+
+Requires Python 3.11+, Django 5.2+ and harel 0.10+. Alpha: the API may still change.
+
+```
+event Submit  {}
+event Approve {}
+event Reject  { note: string }
+
+machine publishing {
+  context { article_id: int }
+
+  initial Draft
+
+  state Draft    {}
+  state InReview { on enter articles.actions.on_in_review }
+  state Approved {}
+
+  final Published success { on enter articles.actions.on_published }
+  final Rejected  failure { on enter articles.actions.on_rejected }
+
+  from Draft    to InReview on Submit
+  from InReview to Approved on Approve
+  from Approved to Published
+  from InReview to Rejected on Reject
+}
+```
+
+## Two ways to run a machine
+
+**In the background**, like Celery, but with the coordination in the machine rather than in
+chained tasks and status fields. The request records the event and answers at once. A worker
+runs it. Waiting days for a webhook, retrying with back-off, timing out, fanning out and
+joining are all part of the machine. A machine waiting for its next event is just a row.
+
+**In the request**, for flows the user drives step by step: wizards, checkouts. The request
+runs the event to the end and renders the new state. There is no queue and no worker.
+
+## Transactions
+
+Everything goes through the connection Django already has, so it joins your transactions:
+
+```python
+class Article(models.Model):
+    ...
+    publishing = ExecutionField("publishing", autostart=True)
+
+
+with transaction.atomic():
+    article = Article.objects.create(...)   # its publishing execution starts with it
+```
+
+If the block rolls back, the execution and its queued `Start` roll back with the article. No
+worker ever runs a workflow for a row that doesn't exist, and you never need
+`transaction.on_commit()`.
+
+On the worker, each event is a transaction too: what its actions write, the machine's step and
+the acknowledgement commit together. A worker that dies halfway leaves nothing behind.
+
+## Install
+
+```bash
+pip install django-harel
+```
+
+```python
+INSTALLED_APPS = [..., "django_harel"]
+
+DJANGO_HAREL = {
+    "MACHINES": {"publishing": "articles/machines/publishing.stm"},
+}
+```
+
+```bash
+python manage.py migrate
+python manage.py harel_worker
+```
+
+## Use
+
+```python
+article.publishing.send("Submit")             # background: queued, the worker runs it
+article.publishing.state                      # "InReview"
+
+order.checkout.process("Pay", token=token)  # in the request: runs now, in this transaction
+```
+
+`ExecutionField` ties a machine to a model; the runners underneath (`distributed_runner()`,
+`durable_runner()`) work for executions that don't belong to a row.
+
+The Django admin's **Machines** catalog lists every machine: its diagram, what it invokes, its
+top-level executions, and their counts by status. It also shows the queue by machine and every
+worker's heartbeat. It flags work no live worker claims, a timer nothing is firing, and a worker
+that is gone. From the executions list you can suspend, resume, cancel, terminate, redrive or
+purge them.
+
+Signals (`step_committed`, `execution_finished`, `execution_failed`) tell your code about every
+step, once its transaction has committed.
+
+## Example
+
+[`example/`](https://github.com/acasadom/django-harel/tree/main/example) is a Django app with
+a REST API (django-ninja) and a worker, on PostgreSQL with `docker compose up`. It has two machines:
+
+- **articles**: the publishing workflow above, the one the tutorial builds.
+- **orders**: shipping and billing in parallel regions, one parcel per item (a fan-out),
+  payment timers, and a refused card to redrive from the admin.
+
+See [`example/README.md`](https://github.com/acasadom/django-harel/blob/main/example/README.md).
+
+## Documentation
+
+[acasadom.github.io/django-harel](https://acasadom.github.io/django-harel/)
+
+## License
+
+Apache 2.0

django_harel-0.1.0/pyproject.toml

@@ -0,0 +1,84 @@
+[project]
+name = "django-harel"
+dynamic = ["version"]
+description = "Django integration for harel statecharts — a Celery alternative for state-machine-shaped work"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Alberto Casado" }]
+keywords = ["statechart", "state-machine", "django", "celery", "durable-execution", "workflow"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Framework :: Django",
+    "Framework :: Django :: 5.2",
+    "Framework :: Django :: 6.0",
+    "Intended Audience :: Developers",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Typing :: Typed",
+]
+requires-python = ">=3.11,<4"
+dependencies = [
+    "harel>=0.10.0",
+    "django>=5.2",
+]
+
+[project.urls]
+Homepage = "https://github.com/acasadom/django-harel"
+Repository = "https://github.com/acasadom/django-harel"
+Issues = "https://github.com/acasadom/django-harel/issues"
+
+[dependency-groups]
+dev = [
+    "pytest",
+    "pytest-django",
+    "ruff",
+    "mypy",
+    "django-stubs",
+    "harel[lsp]>=0.10.0",
+    "django-ninja",
+    "psycopg[binary]>=3.3.6",
+    "pymysql>=1.2.3",
+]
+
+[build-system]
+requires = ["hatchling", "hatch-vcs"]
+build-backend = "hatchling.build"
+
+[tool.hatch.version]
+source = "vcs"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/django_harel"]
+
+[tool.hatch.build.targets.sdist]
+include = ["/src/django_harel", "/tests", "/README.md", "/CHANGELOG.md", "/LICENSE", "/pyproject.toml"]
+
+[tool.pytest.ini_options]
+pythonpath = ["src", "."]
+testpaths = ["tests"]
+DJANGO_SETTINGS_MODULE = "tests.settings"
+
+[tool.ruff]
+line-length = 110
+target-version = "py311"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "W"]
+ignore = ["E501"]
+
+[tool.ruff.lint.isort]
+known-first-party = ["django_harel"]
+
+[tool.mypy]
+files = ["src"]
+plugins = ["mypy_django_plugin.main"]
+ignore_missing_imports = true
+check_untyped_defs = true
+
+[tool.django-stubs]
+django_settings_module = "tests.settings"

django_harel-0.1.0/src/django_harel/__init__.py

@@ -0,0 +1,14 @@
+from django_harel.conf import definitions, distributed_runner, durable_runner
+from django_harel.fields import ExecutionField, instance_for
+from django_harel.store import DjangoStore
+from django_harel.transport import DjangoTransport
+
+__all__ = [
+    "DjangoStore",
+    "DjangoTransport",
+    "ExecutionField",
+    "definitions",
+    "distributed_runner",
+    "durable_runner",
+    "instance_for",
+]