Django Report Engine provides a reporting framework for Django 1.3+. Its goal is to be lightweight, provide multiple output formats, easily integrate into existing applications, and be open ended to both direct SQL reports, ORM based reports, or any other type of report imaginable. It is also attempting to be reasonably batteries-included with some basic Date based filtering assumptions, and simple namespacing of reports.
Reports are assumed to be tabular, with additional key/value “aggregates”. A special form can be used to provide filtering/querying controls. There are premade filtering controls/framework to assist. Existing shortcut queryset and SQL based forms are integrated and can be quickly extended for generic reports. CSV, XML and HTML exports are included.
Metadata
Release files for django-reportengine 0.3.1
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 | |
|---|---|---|---|---|
| django-reportengine-0.3.1.tar.gz | 22.3 kB | Without provenance | Details |
Release files / django-reportengine-0.3.1.tar.gz
| Download URL | django-reportengine-0.3.1.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ce14f7e3a6378f58a8975aef15f2534972406801e4b977882dd6dd73b880e1c
|
|
BLAKE2b-256 checksum How to use checksums |
63a4fb4f1fd0a053c7403a3b34bf4c110d2413f1022136f4b6c29cc0fca6940c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-reportengine 0.3.1
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.