django-drynk gives you DRY natural keys.
Instead of defining a natural_key method on the Model and a get_by_natural_key method on the Manager, instead you add a simple decorator to your model which takes care of everything.
1 maintainer
Metadata
1 maintainer
Release files for django-drynk 0.1.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-drynk-0.1.2.tar.gz | 5.1 kB | Without provenance | Details |
Release files / django-drynk-0.1.2.tar.gz
| Download URL | django-drynk-0.1.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d83895df1fa3228524428fed695718e97cb9d2d2d83f27a2927340752d46d0e
|
|
BLAKE2b-256 checksum How to use checksums |
615b98076b6dd98e652a46afc5b557eb468ca7a996ab48c043451e9716ff7ee7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-drynk 0.1.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.
