h1. huDjango
huDjango contains a collection of small extensions th the [http://www.djangoproject.com/ Django Web framework] we use at HUDORA.
auth.backends.!EmailBackend - Authenticate against django.contrib.auth.models.User the same way Django does by default except that the users can use their E-Mail address instead of the username to authenticate.
auth.backends.!ZimbraBackend - Authenticate against a Zimbra Server via LDAP. Users have to use their full E-Mail adress and Zimbra Passwort to log in. The Backend creates a new entry in the Django User Database if authentication against Zimbra is successfull but no matching E-Mail in Django adress is found.
fields.scalingimagefield - images with automatic scaling
fields.defaulting - Django fields with more elaborate default values
templatetags.hudjango - format_address tag for formating the AddressProtocol, html_euro, html_cent, g2kg and link_object tags.
PrinterChooser - selection of a printer which is stored in a cookie.
serializers.queryset_to_xls - generate Excel/XLS file from a queryset.
h2. Download
You can get huDjango at the “Python Cheeseshop”:http://pypi.python.org/pypi/huDjango/ or at “GitHub”:http://github.com/hudora/huDjango.
h2. Changes
0.91: dedupingS3storage.DedupingS3storage.py dtores file in S3 merging duplicate files
0.90: decorators.ajax_request(), New CouchDB stuff: CouchDBField and CouchDB template loader
0.88: format_addressproto() now understands dicts
0.86: added serializers.queryset_to_xls, fixes for require_login and ZimbraBackend
0.85: deUmlaut template filter
0.84: format_addressproto, more robust clienttracking, don’t generate links for empty image IDs, fixed {% imageid … urlonly %} templatetag
0.83: hudjango.auth.decorators.require_login implements a bridge between Apache HTTP authentication and Django sessions
0.82: Storage Modules, huImage
0.78: hudjango.!PrinterChooser() functionality and respective template tags.
0.77: Django 1.0 compatibility
0.74: template tags / filters now work with Djangos new [http://www.djangoproject.com/documentation/templates/#autoescape autoescape] functionality. Needs Django version > r6844.
0.73: Extracted templatetags from the internal MoftS codebase.
0.72: removed hudjango.fields.audit , support for Django Revision 7403.
h2. Alternatives
Metadata
Release files for huDjango 0.95p1
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 |
|---|---|---|---|---|
| huDjango-0.95p1.tar.gz | 34.3 kB | Without provenance | Details for huDjango-0.95p1.tar.gz |
Release files / huDjango-0.95p1.tar.gz
| Download URL | huDjango-0.95p1.tar.gz |
|---|---|
| Size | 34.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8119c2162b6d561074f728b62639d94ed7ab7275061a927dd97789dfb40cc8a1
|
|
BLAKE2b-256 checksum How to use checksums |
878dac211dc883a6b6fa42f1b6570ce7efab3545dc6d70f9c73a99b6b81243bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for huDjango 0.95p1
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.