Django common application
Django-common provides useful shortcuts for developing django projects.
Overview
context_processors
settings_processor - put django.conf.settings into RequestContext
decorators
render_to - classic render_to functionality
paged - paginate the response_qs variable in response. Used with render_to.
ajax - wrap view reponse into JSON
fields
AutoOneToOneField - OneToOne field which automatically creates related object
forms
build_form - shortcut for creating GET/POST form with one line of code
http
HttpResponseJson - Response class which wraps data into JSON format. Used in common.decorators.ajax
middleware
LoginRequiredMiddleware - restrict guest access
1 maintainer
Metadata
1 maintainer
Release files for django-common 0.1.51
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-common-0.1.51.tar.gz | 14.6 kB | Without provenance | Details for django-common-0.1.51.tar.gz |
Release files / django-common-0.1.51.tar.gz
| Download URL | django-common-0.1.51.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b9921d607d05cce6d94aa70c1fc2ec584b6f0987126d8a746c1b9fc2dc11aefa
|
|
BLAKE2b-256 checksum How to use checksums |
13323b00c64691e56386f88c1e4d2fbef9f26cfc7e11b1d396e482269f63013e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-common 0.1.51
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.
