It uses a view to get the choices and YUI for the js implementation. A demo application is included in the repository.
If you find bugs or have enhancements/proposals please submit a ticket at bitbucket.
If you have feedbacks, send them to me by email.
1 maintainer
Metadata
1 maintainer
Release files for django-autocomplete 0.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-autocomplete-v0.1.tar.gz | 3.7 kB | Without provenance | Details |
Release files / django-autocomplete-v0.1.tar.gz
| Download URL | django-autocomplete-v0.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7230a24e677381815454aa8787a8419268d7a9d8c43890b32294f1eb5d3014e4
|
|
BLAKE2b-256 checksum How to use checksums |
d03772e9d13129f0e7225de74938e319ac6a116f5bec8ec94c519ee5bf1f065c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-autocomplete 0.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.
