There are a lot of Django versioning apps out there, either in a state of decrepitude, or functional but with a colvoluted or suboptimal design. This app intends to become the de-facto standard to manage revisions in Django.
Recently crawled out of alpha and has a good test suite, but it’s not quite production-grade. Just so y’know.
1 maintainer
Metadata
1 maintainer
Release files for django-revisions 0.3
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-revisions-0.3.tar.gz | 11.6 kB | Without provenance | Details |
Release files / django-revisions-0.3.tar.gz
| Download URL | django-revisions-0.3.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75946b3b3281e1fbf491d62ceee312895b1f774184c48ab9c84220d8411a7939
|
|
BLAKE2b-256 checksum How to use checksums |
7eb3a86fb5e55999e2cd04d022c0cbd739a559c1a6f5d71aa21dc8c5fee8c2db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-revisions 0.3
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.
