install djcli with pip,
go in a directory where you have a Django project,
run djcli
Refer to djcli/tests/*.txt for reference output.
[jpic@hack djcli]$ djcli djcli: time for CLI party ! Will try to auto-detect $DJANGO_SETTINGS_MODULE by searching for settings.py from the current directory. help Get help for a command. chpasswd Change the password for user. dbcheck Check all database connections. delete Delete a model filtered with kwargs. detail Print detail for a model. ls Search models run Execute a callback in Django context. save Update or create a model. setting Show settings from django. settings Print out DJANGO_SETTINGS_MODULE.
Metadata
Release files for djcli 1.6.5
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 |
|---|---|---|---|---|
| djcli-1.6.5.tar.gz | 5.2 kB | Without provenance | Details for djcli-1.6.5.tar.gz |
Release files / djcli-1.6.5.tar.gz
| Download URL | djcli-1.6.5.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a46d3690e38c927fbc6a9b3f237ea2ba97b6ed0d80e2e91aa573dee3fa056cd6
|
|
BLAKE2b-256 checksum How to use checksums |
f22a6eaffdd1a456a10647d513deb75f9ff2e752c87e1a2cf6349cc0414c4e4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.10.1
|
Security for djcli 1.6.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.