Django includes the django-admin command. I really want to spell it django. I also wanted to be able to configure a default settings module in a configuration file.
Usage
pip install django-cmd
django startproject
Once installed, you can use the django command the same as you would normally use the django-admin command.
Replace manage.py
Did you know that the manage.py script is just a thin wrapper around the django-admin command? All the wrapper does is set DJANGO_SETTINGS_MODULE so that it can load your settings and find any additional commands from your installed apps. With a tiny bit of configuration, you can use this django command in place of python manage.py!
In your pyproject.toml file, add a section like this to configure your default settings module:
[tool.django]
settings = "myproject.settings"
# pythonpath = "src" # Default: the pyproject.toml directory
Now you can also use the django command everywhere you would normally use python manage.py:
django runserver
django migrate
django createsuperuser
Metadata
Release files for django-cmd 3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_cmd-3.0.tar.gz | 7.4 kB | With provenance | Details for django_cmd-3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_cmd-3.0-py3-none-any.whl | Python 3 | none | any | Details for django_cmd-3.0-py3-none-any.whl |
Total release size: 11.5 kB
Release files / django_cmd-3.0.tar.gz
| Download URL | django_cmd-3.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
febaed27da7a6e698492910a1f5e59496bdc81672af30f7c63913f08a8d409c1
|
|
BLAKE2b-256 checksum How to use checksums |
619a48fddb91761cf033fa27e74fa31756bdeab65124a780203bfba29772c638
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 26, 2025.
Transparency logRelease files / django_cmd-3.0-py3-none-any.whl
| Download URL | django_cmd-3.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d63ba4f7fc30f3fa592a15585ebf74857f8442f5c0e06fe1934ca35028b3edc
|
|
BLAKE2b-256 checksum How to use checksums |
312f2ac4bad36a006c88873ac72125992794e9affc405064324f60321f7e9d9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 26, 2025.
Transparency logSecurity for django-cmd 3.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.
Attestation for django_cmd-3.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 Dec 26, 2025.
Transparency logA 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.