Easy to use AJAX library for django, all the presentation logic resides outside the views and doesn’t require any JS Framework. Dajaxice uses the unobtrusive standard-compliant (W3C) XMLHttpRequest 1.0 object.
1 maintainer
Metadata
1 maintainer
Release files for django-dajaxice 0.7
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-dajaxice-0.7.tar.gz | 24.6 kB | Without provenance | Details |
Release files / django-dajaxice-0.7.tar.gz
| Download URL | django-dajaxice-0.7.tar.gz |
|---|---|
| Size | 24.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75dda8b83aa41ff42fa29a99f993b70bee5b448a0c1d9d795db127f42ab706d1
|
|
BLAKE2b-256 checksum How to use checksums |
b37ecc2330c3f25d37b1336a6faef4f08b857f0d4bff9eb605b85483f42e49fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-dajaxice 0.7
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.
