The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dvenv 0.1.4
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 | |
|---|---|---|---|---|
| dvenv-0.1.4.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dvenv-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.9 kB
Release files / dvenv-0.1.4.tar.gz
| Download URL | dvenv-0.1.4.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
12530893a471d53f4da9c35f591d678ab714fc106fbdef4b7e34dc78f1540989
|
|
BLAKE2b-256 checksum How to use checksums |
cd8de33955601045f3c95ad46932b3137ebe86ec161e5f3b308979b766362b63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.8.2 Darwin/20.3.0
|
Release files / dvenv-0.1.4-py3-none-any.whl
| Download URL | dvenv-0.1.4-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68cf037eb1f89c8fc85fa7f641ec68bc0157872922cfa8ce8acdf8b100913ddd
|
|
BLAKE2b-256 checksum How to use checksums |
af1730998695a38da63f5bdd1382090882a092d995b139bcddbf4eb787e0561a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.8.2 Darwin/20.3.0
|
Security for dvenv 0.1.4
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.
