The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for django-model-settings 0.3.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-model-settings-0.3.1.tar.gz | 13.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_model_settings-0.3.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 30.6 kB
Release files / django-model-settings-0.3.1.tar.gz
| Download URL | django-model-settings-0.3.1.tar.gz |
|---|---|
| Size | 13.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
133f86606b50efbf53b21c73e50d2adcf29bc3108691900584e4bf981198748a
|
|
BLAKE2b-256 checksum How to use checksums |
264766ac4f00b5bae9377aef01cb76eba80b43aee59facaccb4d6fdadf9b1a37
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_model_settings-0.3.1-py2.py3-none-any.whl
| Download URL | django_model_settings-0.3.1-py2.py3-none-any.whl |
|---|---|
| Size | 17.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f61e56938986bb8e7d53a99c2567e0f8784f4e70d07866d1d2111a4e4105b29b
|
|
BLAKE2b-256 checksum How to use checksums |
a24f9d4046ea81f62e794900b8c8ef76aeeb9e5b388fa70f7ec34b70860117cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-model-settings 0.3.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.
