django-compose 0.1.0.dev1__tar.gz

django_compose-0.1.0.dev1/.gitignore

@@ -0,0 +1,12 @@
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+dist/
+build/
+*.egg-info/
+test-results/

django_compose-0.1.0.dev1/AGENTS.md

@@ -0,0 +1,27 @@
+# django-compose
+
+This is an independent Django composition library. Consumers depend on this
+package; this package never imports a consumer framework, host, or product.
+`docs/SPEC.md` owns the contract. Read it before changing a public seam.
+
+Find the owner first. Django owns application identity and population, model
+construction, fields, managers, migration state, execution, routing, and history.
+This package owns only the missing composition, deterministic emission, and
+reusable migration binding seams. Do not add parallel registries or parsers.
+
+Keep entrypoints thin, names consistent, and policy on the owning object.
+Preserve native extension points and fail explicitly on competing declarations.
+Delete obsolete paths rather than leave competing implementations. Changes must
+agree with their docs and tests. Do not copy implementation files from another
+repository; reconstruct behavior through the public native owners.
+
+Use jj for version-control writes. Do not rewrite published history. Each agent
+owns a separate workspace and a disjoint file set; never revert another lane.
+Read files before and after editing. Keep scratch and evidence outside source.
+Run `make check` and `make dist-check` before delivery. Report checks not run.
+Never run or modify a consumer's live stack to validate this independent library.
+
+Public docs contain durable contracts and contributor guidance. Private plans,
+lane reports, and review receipts belong in the adjacent work-state workspace.
+Publication requires explicit authorization; building and local commits do not
+publish the package.

django_compose-0.1.0.dev1/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog
+
+## 0.1.0.dev1
+
+- Report the composition lock path and wait duration when another reader or
+  writer blocks a build, without assuming that a development server holds it.
+- Publish checked wheel and source archives through the GitHub release workflow.
+- Keep the `typing` extra installable from PyPI with the published
+  `angee-django-stubs`, `angee-django-stubs-ext`, and `angee-mypy` forks.
+- Give `settings.COMPOSE_SNAPSHOT` and `settings.COMPOSE_CLOSURE` their exact
+  native types while preserving Django's ordinary settings diagnostics.
+- Expose `apply_app_settings(namespace, closure)` for applying selected apps'
+  settings contributions to a project with ordinary authored concrete models.
+
+## 0.1.0.dev0 — unreleased
+
+- Compose reusable Django source apps and extension classes into ordinary
+  concrete models with `concrete`, `extends`, `inherits` and `demands` declarations.
+- Configure project settings through `configure(globals())`, with native
+  app dependencies, django-yamlconf contributions and immutable inputs.
+- Verify generated output under a shared startup lock through native ready
+  callbacks, and reject stale or altered output before model population.
+- Optionally select installed apps through entry-point and dependency metadata.
+- Keep native migration history when an app is disabled; bind reusable authored
+  transitions and guard automatic destructive changes across routed databases.
+- Audit retained migration imports and installed providers before a proposed
+  distribution removal, with explicit unsupported/unresolved results.
+- Offer advanced composed-model typing through pinned django-stubs/mypy forks;
+  base dependencies are Django, packaging and django-yamlconf.
+- Include a plain Django example, user guides and fresh installed-wheel checks.
+- Render declared artifacts in models and ready phases, then finalize publication;
+  expose verified artifact paths and receipt leases to startup and serving readers.
+- Compose native URL declarations, ASGI mounts/protocols and ordered lifespans.
+- Recompose before native development-server children start, report inputs before
+  reads and recover after failed composition and file creation/deletion.
+- Inspect installed addon metadata without importing app modules and project
+  generated model typing in memory without rewriting source or stub files.

django_compose-0.1.0.dev1/CONTRIBUTING.md

@@ -0,0 +1,67 @@
+# Contributing
+
+Use Python 3.14 and read [AGENTS.md](AGENTS.md), the
+[documentation index](docs/README.md), and the [specification](docs/SPEC.md) for the
+area you change. This is an independent Django library: reproduce behavior in a
+plain Django project, without requiring a downstream framework or live deployment.
+
+## Set up and check
+
+From the repository root, with uv installed:
+
+```sh
+uv sync --frozen --all-extras
+make check
+make dist-check
+```
+
+The full contributor environment includes the advanced typing extra and its
+pinned published forks; see [dependencies](docs/dependencies.md). The user
+[quick start](docs/quickstart.md) needs only base dependencies.
+
+`make check` runs Ruff lint/format checks, mypy and pytest. For a focused test
+while developing, use the same environment, for example:
+
+```sh
+uv run --no-sync pytest -q tests/test_migrations.py
+```
+
+`make dist-check` builds wheel and sdist, checks metadata and archive contents,
+and exercises a fresh wheel installation outside the checkout. The installation
+test first uses base dependencies, then installed addon wheels with settings
+contributions; it covers composition, native migration history, serving, ORM behavior, stale
+output refusal and retained-import reporting. CI runs the same Makefile targets.
+The Checks workflow uploads archives without publishing them. The separate
+[release workflow](docs/packaging.md#publish-this-library) publishes checked
+archives to PyPI when explicitly dispatched or triggered by a version tag.
+
+## Keep behavior with its owner
+
+Django owns app identity/population, model construction, fields, managers, ORM,
+migration state and execution. Extend those native contracts instead of adding
+parallel registries, parsers or lifecycle systems. django-compose owns only the
+composition, deterministic output and reusable migration-binding seams.
+
+Keep commands and other entrypoints thin. Put a missing rule on its existing
+owner, migrate callers and remove superseded code and guidance. Public behavior,
+types, docstrings, examples and documentation must agree. Changes to a public
+invariant or extension contract use the [proposal process](docs/proposals/README.md).
+
+Tests that configure Django use subprocesses or isolated native registries so
+settings and app state do not leak between cases. Use temporary SQLite databases
+for database behavior and native routers for multiple-database tests. Correct
+safety failures at their owner or in the fixture.
+
+## Source and review
+
+Use Jujutsu for repository writes. Parallel work uses separate workspaces and
+explicit file ownership; preserve other contributors' changes. Keep disposable
+runtimes, caches and reports outside tracked source. A project's native migration
+history is authored source and must survive generation and cleanup.
+
+Commit coherent changes locally. Publication requires the repository owner's
+instructions. Before release, review architecture and Django behavior
+independently as well as running the checks. Promote accepted contract changes
+into current documentation; proposals record decisions rather than maintaining
+a second API reference. Preserve license notices and attribution when changing
+or distributing code.