A slug field that automatically calculates its value from another attribute or method.
Requirements
django-aislug depends on django-stringfield.
Installation
Using pip to install will install django-aislug and all of its dependencies:
pip install django-aislug
Options
All options that are available for django.db.models.CharField are also available to AISlugField. There are some additional options:
populate_from: Property or method on the model that is the base for the computed slug.
Default 'title'
slugify: User defined slugify callback function to compute the slug from populate_from
invalid: List or function that returns a list of invalid values
Default: []
update: If False the slug will not be updated from populate_from on subsequent saves.
Default: False
unique_for: A list of fields to make this slug unique for.
Default: []
Release files for django-aislug 0.2.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-aislug-0.2.2.tar.gz | 4.3 kB | Without provenance | Details |
Release files / django-aislug-0.2.2.tar.gz
| Download URL | django-aislug-0.2.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d114557cbba27b39eab1a24bc387ad1dbe90a2f85d0bbd0bd20fe22da7059c2a
|
|
BLAKE2b-256 checksum How to use checksums |
77e6dd74c79b9acfc8caaffc3fba6db1416a831e1ccc54cb141ec21a6d43b17a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-aislug 0.2.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.
