autoreport for django
Requirements
Tested with Django 1.1.1. Requires relatorio.
How to use it
Install it by adding ‘autoreport’ to INSTALLED_APPS in your settings, (it requires running syncdb again for new models to be installed).
Then, add a line like this into your main URLConf:
(r’^autoreport/’, include(‘autoreport.urls’)),
You should overwrite templates from autoreport’s templates folder in order to match your project.
1 maintainer
Metadata
1 maintainer
Release files for autoreport 0.1.2
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 | |
|---|---|---|---|---|
| autoreport-0.1.2.tar.gz | 3.7 kB | Without provenance | Details |
Release files / autoreport-0.1.2.tar.gz
| Download URL | autoreport-0.1.2.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26abcf50765abbc5f796ddcda7117b93174f5c4e3af81214213126a442eb2ce0
|
|
BLAKE2b-256 checksum How to use checksums |
14967b58418d622dc73743d82fb42b8a1ea3e98eeae5a792de5ad41ca32b38c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for autoreport 0.1.2
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.
