Skip to main content

django-spec-cli

CI PyPI Python versions Django versions Docs Coverage Ruff License

Run a django-service-specs registry from manage.py: one subcommand per spec, an option for each of its parameters, a principal named on the command line, and an exit code for every refusal.

It is the kernel's management-command transport, moved out of the kernel with its history so the kernel carries no transport. The command line, the exit codes and the SpecCommand subclass contract are the ones the kernel shipped; the import path, the system check ids and the setting key are this package's.

Install

pip install django-spec-cli

Python 3.10 or later, Django 4.2 or later, and django-service-specs 0.10.0 or later, which it installs.

Quickstart

Subclass SpecCommand in one of your apps' management/commands/ modules and name a registry; the module's name is the command's:

# yourapp/management/commands/notes.py
from django_spec_cli import SpecCommand

from yourapp.specs import notes  # a django_service_specs.SpecRegistry


class Command(SpecCommand):
    registry = notes
$ python manage.py notes rename-note --as-user 1 --pk 1 --title Final --json
{"id":1,"title":"Final"}

The run goes through the kernel's dispatch, so the permission checks are enforced for the user --as-user names. --explain lists the specs that authorize nothing.

The system check

List "django_spec_cli" in INSTALLED_APPS and manage.py check reports every open spec a SpecCommand serves as django_spec_cli.W001, and a command that could not be loaded as django_spec_cli.W003. The command itself needs no app listed.

Until the kernel removes its own copy of the command, kernel 0.10.x still registers django_service_specs.W001 and W003 over its own SpecCommand. A project listing both "django_service_specs" and "django_spec_cli" sees both ids: each walk reports the commands subclassing its own class, and a command that cannot be loaded is reported by each. A project that moves its imports here and lists only "django_service_specs" gets no check for the moved commands, so list "django_spec_cli".

Documentation

https://artui.github.io/django-spec-cli/

License

MIT. See LICENSE.

Metadata

Release files for django-spec-cli 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for django-spec-cli 0.1.0
File Size Uploaded Provenance
django_spec_cli-0.1.0.tar.gz 191.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for django-spec-cli 0.1.0
File Interpreter ABI Platform
django_spec_cli-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 226.7 kB

Release files / django_spec_cli-0.1.0.tar.gz

Download URL django_spec_cli-0.1.0.tar.gz
Size 191.4 kB
Tags Source
SHA-256 checksum
How to use checksums
3176387c4649b3b5e1a2e114a9441ea0776e52dd8178f115bab3529a2aff1b5a
BLAKE2b-256 checksum
How to use checksums
859b1f08b5ff4fc4a84425e889151fa2189fc15fc0063b909b9b0c1d6b32a3bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 20, 2026.

Transparency log

Release files / django_spec_cli-0.1.0-py3-none-any.whl

Download URL django_spec_cli-0.1.0-py3-none-any.whl
Size 35.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
27567a0e42d462500521a7a1e86013e83eb28ad342b1e017f8394886a4baf7c2
BLAKE2b-256 checksum
How to use checksums
4fa2a5fb9b45fa74222d11ea0a46eedec893ef36b8bf535dae28af0812b51512
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 20, 2026.

Transparency log

Security for django-spec-cli 0.1.0

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.

Select from 2 files

Attestation for django_spec_cli-0.1.0.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 20, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page