django-tunables 0.1.0__tar.gz

django_tunables-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ekiourk consulting ltd
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

django_tunables-0.1.0/PKG-INFO

@@ -0,0 +1,265 @@
+Metadata-Version: 2.4
+Name: django-tunables
+Version: 0.1.0
+Summary: Runtime-tunable parameters for Django with change sets, versioned snapshots and schema-described forms.
+Author: Ilias Kiourktsidis
+License: MIT
+Project-URL: Homepage, https://github.com/ekiourk/django-tunables
+Project-URL: Repository, https://github.com/ekiourk/django-tunables
+Project-URL: Changelog, https://github.com/ekiourk/django-tunables/blob/master/CHANGELOG.md
+Keywords: django,settings,configuration,feature-flags,audit,rest
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 5.2
+Classifier: Framework :: Django :: 6.0
+Classifier: Framework :: Django :: 6.1
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: Django>=5.2
+Requires-Dist: djangorestframework>=3.15
+Provides-Extra: dev
+Requires-Dist: pytest; extra == "dev"
+Requires-Dist: pytest-cov; extra == "dev"
+Requires-Dist: pytest-django; extra == "dev"
+Requires-Dist: jsonschema[format]; extra == "dev"
+Requires-Dist: django-tunables[fixtures]; extra == "dev"
+Requires-Dist: ipdb; extra == "dev"
+Provides-Extra: fixtures
+Requires-Dist: testcontainers[postgres]==4.12.0; extra == "fixtures"
+Requires-Dist: psycopg[binary]; extra == "fixtures"
+Provides-Extra: lint
+Requires-Dist: ruff; extra == "lint"
+Requires-Dist: mypy; extra == "lint"
+Requires-Dist: django-stubs; extra == "lint"
+Requires-Dist: djangorestframework-stubs; extra == "lint"
+Dynamic: license-file
+
+# django-tunables
+
+Runtime-tunable parameters for Django with a full audit trail. The host project declares
+a catalogue of parameters in Python: keys, types, defaults, constraints, grouping.
+Operators change values through the Django admin or a REST API. Every change is an
+atomic, versioned change set, and every version produces a snapshot: one JSON document
+holding the complete effective parameter set, ready for other processes to read from
+the database or a file. Each group can also be described as JSON Schema plus a UI
+schema, so an external client can render its own editing forms.
+
+It is not a replacement for Django settings, and it does not patch `django.conf.settings`.
+It has no per-user, per-tenant or per-environment scopes; one database holds one
+catalogue with one effective value per key. Scheduled changes, nullable values, and
+notifications beyond the publisher hook are out of scope.
+
+## How it differs from django-constance and django-dynamic-preferences
+
+Both of those store dynamic settings in the database and edit them in the admin.
+django-tunables adds change sets with actor and reason, an append-only history, a
+snapshot per version that other processes can read without importing the package, and a
+schema endpoint that describes each group to external clients. Two ideas were borrowed:
+the type to form field mapping comes from constance, and giving each type its own form
+field, serializer and validator comes from dynamic-preferences.
+
+## Requirements
+
+Python 3.12 or newer, Django 5.2 or newer, Django REST Framework 3.15 or newer.
+PostgreSQL 14 or newer for the optional database-level history protection. SQLite works
+for everything else.
+
+```
+pip install django-tunables
+```
+
+## Quickstart
+
+Add the apps and point the setting at your catalogue. In `settings.py`:
+
+```python
+INSTALLED_APPS = [
+    # ...
+    "rest_framework",
+    "tunables",
+]
+
+TUNABLES = {"CATALOGUE": "myproject.tunables_catalogue.catalogue"}
+```
+
+Declare the catalogue. In `myproject/tunables_catalogue.py`:
+
+```python
+from tunables import Boolean, Catalogue, Enum, Float, Group, List, Tunable
+
+pricing = Group(
+    "pricing",
+    title="Pricing",
+    order=1,
+    tunables=[
+        Tunable("vat_rate", Float(min=0.0, max=1.0), 0.24, title="VAT rate"),
+        Tunable("free_shipping_over", Float(min=0.0), 50.0, title="Free shipping over", unit="EUR"),
+        Tunable("currencies", List(Enum(["EUR", "USD", "GBP"]), min_items=1, unique=True), ["EUR"]),
+        Tunable("allow_backorders", Boolean(), False),
+    ],
+)
+
+thermostat = Group(
+    "thermostat",
+    title="Thermostat",
+    order=2,
+    tunables=[
+        Tunable("target_c", Float(min=5.0, max=30.0), 21.0, title="Target temperature", unit="°C"),
+        Tunable("mode", Enum(["auto", "heat", "cool", "off"]), "auto"),
+    ],
+)
+
+catalogue = Catalogue([pricing, thermostat])
+```
+
+Mount the API next to the admin. In `myproject/urls.py`:
+
+```python
+from django.contrib import admin
+from django.urls import include, path
+
+urlpatterns = [
+    path("admin/", admin.site.urls),
+    path("api/tunables/", include("tunables.api.urls")),
+]
+```
+
+Create the tables and the first snapshot:
+
+```
+python manage.py migrate
+python manage.py tunables_sync
+```
+
+Read the effective values:
+
+```
+curl -s http://localhost:8000/api/tunables/values/
+```
+
+Change one:
+
+```
+curl -s -X POST http://localhost:8000/api/tunables/changesets/ \
+  -H "Content-Type: application/json" \
+  -H "X-Tunables-Actor: alice" \
+  -d '{"changes": [{"key": "pricing.vat_rate", "value": 0.2}], "reason": "autumn rate"}'
+```
+
+The response is the new change set with version 1. `tunables_show` prints the effective
+values with an override marker, and the admin's Tunables page offers the same edit as a
+form. Run `tunables_sync` after every deployment, after `migrate`, so the database
+mirror follows the catalogue in code.
+
+## Settings
+
+All settings live in one dictionary, `TUNABLES`. Only `CATALOGUE` is required.
+
+| Key | Default | Meaning |
+|---|---|---|
+| `CATALOGUE` | required | Dotted path to a `Catalogue` instance or to a zero-argument callable returning one. |
+| `ENVIRONMENT` | `""` | Written into every snapshot document as `environment`. |
+| `PUBLISHERS` | `[]` | Dotted paths of publisher classes, instantiated once with no arguments. |
+| `FILE_PUBLISHER_PATH` | `None` | Target file of `tunables.publishers.FilePublisher`. |
+| `PAGE_SIZE` | `50` | Page size of the change set list endpoint. |
+| `API_AUTHENTICATION_CLASSES` | `None` | DRF authentication classes for the API. `None` uses the host's DRF defaults. |
+| `API_PERMISSION_CLASSES` | `None` | DRF permission classes for the API. `None` uses the host's DRF defaults. |
+| `ACTOR_RESOLVER` | `tunables.api.actors.default_actor_resolver` | Callable turning a request into an `Actor`. |
+| `EDITABLE_GROUPS` | `None` | Callable returning the group names a request may write, or `None` for all. |
+| `ACTOR_HEADER` | `X-Tunables-Actor` | Header naming the actor of an unauthenticated request. |
+| `CLIENT_HEADER` | `X-Tunables-Client` | Header naming the client program. |
+| `REQUEST_ID_HEADER` | `X-Request-ID` | Header whose value is recorded as the change set's request id. |
+
+## Management commands
+
+| Command | Does |
+|---|---|
+| `tunables_sync [--check]` | Mirrors the catalogue into the database, creates the state row and snapshot 0 on a fresh database, and writes a system version when the catalogue structure changed. `--check` exits 1 when the stored catalogue version differs from the code, without writing. Idempotent. |
+| `tunables_show [--group NAME] [--json]` | Prints the effective values of the latest snapshot, one key per line, marking overrides. `--json` prints the snapshot document. |
+| `tunables_export [--output FILE]` | Writes the latest snapshot document as JSON to a file or to standard output. |
+| `tunables_import FILE --actor NAME [--reason TEXT] [--strict]` | Applies the values of a snapshot document as one change set with `source: import`. Unknown keys are skipped with a warning, or rejected with `--strict`. |
+| `tunables_protect_history [--remove] [--database ALIAS]` | Installs PostgreSQL triggers that reject `UPDATE`, `DELETE` and `TRUNCATE` on the history tables. |
+
+`tunables_sync --check` compares the catalogue hash only. A change to a title or
+description makes the mirror stale without changing the hash; the next `tunables_sync`
+updates the mirror without writing a new version.
+
+## Publishers and the signal
+
+The snapshot row in the database is always written. In addition, every committed
+snapshot is sent to the `tunables.signals.snapshot_published` signal, with the
+`Snapshot` instance as `snapshot`, and then to each publisher named in `PUBLISHERS`.
+A publisher is any object with a `publish(snapshot)` method. An exception inside
+`publish` is logged under the `tunables.publishers` logger and does not affect the
+write. Both the signal and the publishers run after the transaction commits.
+
+`tunables.publishers.FilePublisher` writes the document to `FILE_PUBLISHER_PATH`, using
+a temporary file in the same directory and a rename, so readers never see a partial
+file:
+
+```python
+TUNABLES = {
+    "CATALOGUE": "myproject.tunables_catalogue.catalogue",
+    "PUBLISHERS": ["tunables.publishers.FilePublisher"],
+    "FILE_PUBLISHER_PATH": "/var/lib/myproject/tunables.json",
+}
+```
+
+## Reading snapshots from other processes
+
+A reader polls `tunables_state.current_version`, and when it changes fetches
+`tunables_snapshot.document` for that version. The document format, the JSON Schema
+shipped with the package, and the table contract are in
+[docs/snapshot-format.md](docs/snapshot-format.md).
+
+## API
+
+| Method and path | Purpose |
+|---|---|
+| `GET groups/`, `GET groups/{group}/` | groups and their definitions |
+| `GET groups/{group}/schema/`, `GET schema/` | JSON Schema and UI schema |
+| `GET values/`, `GET groups/{group}/values/` | effective values, with `ETag` |
+| `GET changesets/`, `GET changesets/{version}/` | history, paginated and filterable |
+| `GET snapshots/latest/`, `GET snapshots/{version}/`, `GET export/` | snapshot documents |
+| `POST changesets/`, `POST validate/` | apply or dry-run a list of changes |
+| `PATCH groups/{group}/values/` | form-shaped write of one group |
+| `POST rollback/`, `POST import/` | restore a version, import a document |
+
+Writes accept `If-Match` for optimistic concurrency and every response carries
+`X-Tunables-Version`. Errors are RFC 9457 problem documents. The full reference,
+including the problem types and error codes, is in [docs/api.md](docs/api.md).
+
+## Admin
+
+The Tunables page in the admin lists the groups and edits one group per form with a
+reason field and a reset box per override. The change set history is read only and has
+a rollback action. See [docs/admin.md](docs/admin.md).
+
+A screenshot of the group edit form will be added here.
+
+## Documentation
+
+- [Declaring the catalogue](docs/catalogue.md)
+- [REST API](docs/api.md)
+- [Django admin](docs/admin.md)
+- [Snapshot format and reader contract](docs/snapshot-format.md)
+
+## Development
+
+```
+uv sync --all-extras
+uv run pytest
+uv run pytest --postgres    # the whole suite on a PostgreSQL testcontainer, needs Docker
+uv run ruff check . && uv run mypy src
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

django_tunables-0.1.0/README.md

@@ -0,0 +1,222 @@
+# django-tunables
+
+Runtime-tunable parameters for Django with a full audit trail. The host project declares
+a catalogue of parameters in Python: keys, types, defaults, constraints, grouping.
+Operators change values through the Django admin or a REST API. Every change is an
+atomic, versioned change set, and every version produces a snapshot: one JSON document
+holding the complete effective parameter set, ready for other processes to read from
+the database or a file. Each group can also be described as JSON Schema plus a UI
+schema, so an external client can render its own editing forms.
+
+It is not a replacement for Django settings, and it does not patch `django.conf.settings`.
+It has no per-user, per-tenant or per-environment scopes; one database holds one
+catalogue with one effective value per key. Scheduled changes, nullable values, and
+notifications beyond the publisher hook are out of scope.
+
+## How it differs from django-constance and django-dynamic-preferences
+
+Both of those store dynamic settings in the database and edit them in the admin.
+django-tunables adds change sets with actor and reason, an append-only history, a
+snapshot per version that other processes can read without importing the package, and a
+schema endpoint that describes each group to external clients. Two ideas were borrowed:
+the type to form field mapping comes from constance, and giving each type its own form
+field, serializer and validator comes from dynamic-preferences.
+
+## Requirements
+
+Python 3.12 or newer, Django 5.2 or newer, Django REST Framework 3.15 or newer.
+PostgreSQL 14 or newer for the optional database-level history protection. SQLite works
+for everything else.
+
+```
+pip install django-tunables
+```
+
+## Quickstart
+
+Add the apps and point the setting at your catalogue. In `settings.py`:
+
+```python
+INSTALLED_APPS = [
+    # ...
+    "rest_framework",
+    "tunables",
+]
+
+TUNABLES = {"CATALOGUE": "myproject.tunables_catalogue.catalogue"}
+```
+
+Declare the catalogue. In `myproject/tunables_catalogue.py`:
+
+```python
+from tunables import Boolean, Catalogue, Enum, Float, Group, List, Tunable
+
+pricing = Group(
+    "pricing",
+    title="Pricing",
+    order=1,
+    tunables=[
+        Tunable("vat_rate", Float(min=0.0, max=1.0), 0.24, title="VAT rate"),
+        Tunable("free_shipping_over", Float(min=0.0), 50.0, title="Free shipping over", unit="EUR"),
+        Tunable("currencies", List(Enum(["EUR", "USD", "GBP"]), min_items=1, unique=True), ["EUR"]),
+        Tunable("allow_backorders", Boolean(), False),
+    ],
+)
+
+thermostat = Group(
+    "thermostat",
+    title="Thermostat",
+    order=2,
+    tunables=[
+        Tunable("target_c", Float(min=5.0, max=30.0), 21.0, title="Target temperature", unit="°C"),
+        Tunable("mode", Enum(["auto", "heat", "cool", "off"]), "auto"),
+    ],
+)
+
+catalogue = Catalogue([pricing, thermostat])
+```
+
+Mount the API next to the admin. In `myproject/urls.py`:
+
+```python
+from django.contrib import admin
+from django.urls import include, path
+
+urlpatterns = [
+    path("admin/", admin.site.urls),
+    path("api/tunables/", include("tunables.api.urls")),
+]
+```
+
+Create the tables and the first snapshot:
+
+```
+python manage.py migrate
+python manage.py tunables_sync
+```
+
+Read the effective values:
+
+```
+curl -s http://localhost:8000/api/tunables/values/
+```
+
+Change one:
+
+```
+curl -s -X POST http://localhost:8000/api/tunables/changesets/ \
+  -H "Content-Type: application/json" \
+  -H "X-Tunables-Actor: alice" \
+  -d '{"changes": [{"key": "pricing.vat_rate", "value": 0.2}], "reason": "autumn rate"}'
+```
+
+The response is the new change set with version 1. `tunables_show` prints the effective
+values with an override marker, and the admin's Tunables page offers the same edit as a
+form. Run `tunables_sync` after every deployment, after `migrate`, so the database
+mirror follows the catalogue in code.
+
+## Settings
+
+All settings live in one dictionary, `TUNABLES`. Only `CATALOGUE` is required.
+
+| Key | Default | Meaning |
+|---|---|---|
+| `CATALOGUE` | required | Dotted path to a `Catalogue` instance or to a zero-argument callable returning one. |
+| `ENVIRONMENT` | `""` | Written into every snapshot document as `environment`. |
+| `PUBLISHERS` | `[]` | Dotted paths of publisher classes, instantiated once with no arguments. |
+| `FILE_PUBLISHER_PATH` | `None` | Target file of `tunables.publishers.FilePublisher`. |
+| `PAGE_SIZE` | `50` | Page size of the change set list endpoint. |
+| `API_AUTHENTICATION_CLASSES` | `None` | DRF authentication classes for the API. `None` uses the host's DRF defaults. |
+| `API_PERMISSION_CLASSES` | `None` | DRF permission classes for the API. `None` uses the host's DRF defaults. |
+| `ACTOR_RESOLVER` | `tunables.api.actors.default_actor_resolver` | Callable turning a request into an `Actor`. |
+| `EDITABLE_GROUPS` | `None` | Callable returning the group names a request may write, or `None` for all. |
+| `ACTOR_HEADER` | `X-Tunables-Actor` | Header naming the actor of an unauthenticated request. |
+| `CLIENT_HEADER` | `X-Tunables-Client` | Header naming the client program. |
+| `REQUEST_ID_HEADER` | `X-Request-ID` | Header whose value is recorded as the change set's request id. |
+
+## Management commands
+
+| Command | Does |
+|---|---|
+| `tunables_sync [--check]` | Mirrors the catalogue into the database, creates the state row and snapshot 0 on a fresh database, and writes a system version when the catalogue structure changed. `--check` exits 1 when the stored catalogue version differs from the code, without writing. Idempotent. |
+| `tunables_show [--group NAME] [--json]` | Prints the effective values of the latest snapshot, one key per line, marking overrides. `--json` prints the snapshot document. |
+| `tunables_export [--output FILE]` | Writes the latest snapshot document as JSON to a file or to standard output. |
+| `tunables_import FILE --actor NAME [--reason TEXT] [--strict]` | Applies the values of a snapshot document as one change set with `source: import`. Unknown keys are skipped with a warning, or rejected with `--strict`. |
+| `tunables_protect_history [--remove] [--database ALIAS]` | Installs PostgreSQL triggers that reject `UPDATE`, `DELETE` and `TRUNCATE` on the history tables. |
+
+`tunables_sync --check` compares the catalogue hash only. A change to a title or
+description makes the mirror stale without changing the hash; the next `tunables_sync`
+updates the mirror without writing a new version.
+
+## Publishers and the signal
+
+The snapshot row in the database is always written. In addition, every committed
+snapshot is sent to the `tunables.signals.snapshot_published` signal, with the
+`Snapshot` instance as `snapshot`, and then to each publisher named in `PUBLISHERS`.
+A publisher is any object with a `publish(snapshot)` method. An exception inside
+`publish` is logged under the `tunables.publishers` logger and does not affect the
+write. Both the signal and the publishers run after the transaction commits.
+
+`tunables.publishers.FilePublisher` writes the document to `FILE_PUBLISHER_PATH`, using
+a temporary file in the same directory and a rename, so readers never see a partial
+file:
+
+```python
+TUNABLES = {
+    "CATALOGUE": "myproject.tunables_catalogue.catalogue",
+    "PUBLISHERS": ["tunables.publishers.FilePublisher"],
+    "FILE_PUBLISHER_PATH": "/var/lib/myproject/tunables.json",
+}
+```
+
+## Reading snapshots from other processes
+
+A reader polls `tunables_state.current_version`, and when it changes fetches
+`tunables_snapshot.document` for that version. The document format, the JSON Schema
+shipped with the package, and the table contract are in
+[docs/snapshot-format.md](docs/snapshot-format.md).
+
+## API
+
+| Method and path | Purpose |
+|---|---|
+| `GET groups/`, `GET groups/{group}/` | groups and their definitions |
+| `GET groups/{group}/schema/`, `GET schema/` | JSON Schema and UI schema |
+| `GET values/`, `GET groups/{group}/values/` | effective values, with `ETag` |
+| `GET changesets/`, `GET changesets/{version}/` | history, paginated and filterable |
+| `GET snapshots/latest/`, `GET snapshots/{version}/`, `GET export/` | snapshot documents |
+| `POST changesets/`, `POST validate/` | apply or dry-run a list of changes |
+| `PATCH groups/{group}/values/` | form-shaped write of one group |
+| `POST rollback/`, `POST import/` | restore a version, import a document |
+
+Writes accept `If-Match` for optimistic concurrency and every response carries
+`X-Tunables-Version`. Errors are RFC 9457 problem documents. The full reference,
+including the problem types and error codes, is in [docs/api.md](docs/api.md).
+
+## Admin
+
+The Tunables page in the admin lists the groups and edits one group per form with a
+reason field and a reset box per override. The change set history is read only and has
+a rollback action. See [docs/admin.md](docs/admin.md).
+
+A screenshot of the group edit form will be added here.
+
+## Documentation
+
+- [Declaring the catalogue](docs/catalogue.md)
+- [REST API](docs/api.md)
+- [Django admin](docs/admin.md)
+- [Snapshot format and reader contract](docs/snapshot-format.md)
+
+## Development
+
+```
+uv sync --all-extras
+uv run pytest
+uv run pytest --postgres    # the whole suite on a PostgreSQL testcontainer, needs Docker
+uv run ruff check . && uv run mypy src
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

django_tunables-0.1.0/pyproject.toml

@@ -0,0 +1,73 @@
+[project]
+name = "django-tunables"
+version = "0.1.0"
+requires-python = ">=3.12"
+description = "Runtime-tunable parameters for Django with change sets, versioned snapshots and schema-described forms."
+license = {text = "MIT"}
+readme = "README.md"
+authors = [{name = "Ilias Kiourktsidis"}]
+keywords = ["django", "settings", "configuration", "feature-flags", "audit", "rest"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Framework :: Django",
+    "Framework :: Django :: 5.2",
+    "Framework :: Django :: 6.0",
+    "Framework :: Django :: 6.1",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+dependencies = ["Django>=5.2", "djangorestframework>=3.15"]
+
+[project.urls]
+Homepage = "https://github.com/ekiourk/django-tunables"
+Repository = "https://github.com/ekiourk/django-tunables"
+Changelog = "https://github.com/ekiourk/django-tunables/blob/master/CHANGELOG.md"
+
+[project.optional-dependencies]
+dev = ["pytest", "pytest-cov", "pytest-django", "jsonschema[format]", "django-tunables[fixtures]", "ipdb"]
+fixtures = ["testcontainers[postgres]==4.12.0", "psycopg[binary]"]
+lint = ["ruff", "mypy", "django-stubs", "djangorestframework-stubs"]
+
+[build-system]
+requires = ["setuptools>=61.0"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools]
+package-dir = {"" = "src"}
+[tool.setuptools.packages.find]
+where = ["src"]
+[tool.setuptools.package-data]
+tunables = ["py.typed", "schemas/*.json", "templates/**/*.html"]
+
+[tool.ruff]
+src = ["src", "."]
+line-length = 120
+[tool.ruff.lint]
+select = ["E", "W", "F", "I", "B", "C4", "UP", "A", "ARG", "PTH", "SIM", "T20"]
+ignore = ["E501", "B008"]
+[tool.ruff.lint.per-file-ignores]
+"src/tunables/api/views.py" = ["ARG002"]
+"src/tunables/api/writes.py" = ["ARG002"]
+"src/tunables/admin/__init__.py" = ["ARG002"]
+"test_*.py" = ["ARG001", "ARG002"]
+"conftest.py" = ["ARG001", "ARG002"]
+[tool.ruff.format]
+quote-style = "double"
+indent-style = "space"
+
+[tool.mypy]
+python_version = "3.12"
+strict = true
+plugins = ["mypy_django_plugin.main", "mypy_drf_plugin.main"]
+[tool.django-stubs]
+django_settings_module = "tests.settings"
+
+[tool.pytest.ini_options]
+DJANGO_SETTINGS_MODULE = "tests.settings"
+pythonpath = ["."]
+addopts = "--strict-markers"
+markers = ["postgres: needs a PostgreSQL testcontainer"]

django_tunables-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+