Release files for drf-extensions 0.8.0
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 | |
|---|---|---|---|---|
| drf_extensions-0.8.0.tar.gz | 173.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| drf_extensions-0.8.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 195.3 kB
Release files / drf_extensions-0.8.0.tar.gz
| Download URL | drf_extensions-0.8.0.tar.gz |
|---|---|
| Size | 173.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c3f27bca74a2def53e8454a5c7b327595195df51e121743120b2f51ef5a52aaa
|
|
BLAKE2b-256 checksum How to use checksums |
775a57e3cc6f2bb4e1e84ad85eed0a12ddf22d5217b6b87c39e611d10e677a63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Release files / drf_extensions-0.8.0-py2.py3-none-any.whl
| Download URL | drf_extensions-0.8.0-py2.py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ab7bd854c9061c27ab55233b66d758001e5c2d81aaa9d117cbbe1c9ea49c77ab
|
|
BLAKE2b-256 checksum How to use checksums |
aac1b9721c9239b465c0ceac32b33e732c08f6ea0afd8156700e417416a47733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.3
|
Security for drf-extensions 0.8.0
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.
