A Django Admin add-on which adds functionality to export data in customized forms of output,
## Requirements
Django Reports Admin requires Django 1.10 or later, and is written for Python 3.5 or later.
## Installation
pip install django-reports-admin
Then, amend your Django `settings.py` file:
INSTALLED_APPS = (
...
'reports',
...
)
Although enabled by default, you'll want to ensure
`django.contrib.contenttypes`` is within `INSTALLED_APPS`.
## Usage
Creating reports requires subclassing the `ModelReport` class and identifying a
report. This can be done with a few lines of code if you simply want to extract
the admin list view for verbatim. For example:
# This file can be named anything, but it lives well within the admin.py or
# models.py as it'll ensure your register() command is run.
# yourapp/reports.py -- This file can be named anything
from reports.base import ModelReport
class MyReport(ModelReport)
name = "Report - My Report"
Then, register the `ModelReport` against a model:
# yourapp/admin.py
from .reports import MyReport
from .models import MyModel
reports.register(MyModel, MyReport)
Upon registration, you'll see a new action with the Django Admin for that Model,
with whatever name you've provided in the `name` attribute.
For advanced report modification, subclass the following functions within your
`ModelReport` class:
`get_field_lookups` returns a list of column name-value/callback tuples. This
function is a great way to modify the columns of the report, and the exact
output of each field. It is useful if you wish to create a calculated field, or
format a date field.
`get_row_data` returns a dictionary of the data to be entered for each row.
Generally you should not need to modify this as `get_field_lookups` will be
sufficient.
`generate_output` can be modified to adjust the type of output. By default, a
CSV file is generated.
## Testing
Tests are run using `pytest`, and the test suite can be executed using the
MakeFile
make test
# 1.0.0
* Initial release
Metadata
Release files for django-reports-admin 1.0.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 | |
|---|---|---|---|---|
| django-reports-admin-1.0.2.tar.gz | 9.6 kB | Without provenance | Details |
Release files / django-reports-admin-1.0.2.tar.gz
| Download URL | django-reports-admin-1.0.2.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b323ad8100159be8ea8512f1521bfa9bbc80973a565c07f5aba61fca70d0604
|
|
BLAKE2b-256 checksum How to use checksums |
00f5240aa5c1dcdec68d9ca5ce41826b6b26f8c7842f7db2bb3d651b52d5b59a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-reports-admin 1.0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.