1 maintainer
Metadata
1 maintainer
Release files for django-context-from-path 0.1.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_context_from_path-0.1.1.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_context_from_path-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.0 kB
Release files / django_context_from_path-0.1.1.tar.gz
| Download URL | django_context_from_path-0.1.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c459d48fa0a9d40033523d6bbba9c50088c4f8a5e7e968d7c7dbfad5205ca4ac
|
|
BLAKE2b-256 checksum How to use checksums |
e41164be73a72a6e933162e82332ff62d77660ba7a48ffa203ccbe9cb2642c74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / django_context_from_path-0.1.1-py3-none-any.whl
| Download URL | django_context_from_path-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a8cfd9fa4dc8fe04b9f99bfc98e95dbb13a811e70ee6dac600ebf2d81d42836
|
|
BLAKE2b-256 checksum How to use checksums |
526483d47b78162f649c17c629c1a137d2ce24da7c8662b597c29247cbdcc5bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for django-context-from-path 0.1.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.
