The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for autoPyEnV 0.1.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 | |
|---|---|---|---|---|
| autopyenv-0.1.0.tar.gz | 2.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoPyEnV-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.8 kB
Release files / autopyenv-0.1.0.tar.gz
| Download URL | autopyenv-0.1.0.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54d61240494584171e207d8fc29fd8360823025bcb2c4fdac5d8ac000c01a4ad
|
|
BLAKE2b-256 checksum How to use checksums |
0214d396e78ba85e0532f09019c713be088ca4bde93958c770889d21f3eb9961
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Release files / autoPyEnV-0.1.0-py3-none-any.whl
| Download URL | autoPyEnV-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ccd3543b7402b88b724bf1fa67fc346b934bf67da22157dd5902953f69dfb934
|
|
BLAKE2b-256 checksum How to use checksums |
1bf7a9bdef80dcc6da621861c87f6f0ff748fc4e16084b78eed337d2371e52a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.0
|
Security for autoPyEnV 0.1.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.
