The author of this package has not provided a project description
Metadata
Release files for bitcodes-pytorch 0.0.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 | |
|---|---|---|---|---|
| bitcodes-pytorch-0.0.1.tar.gz | 3.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bitcodes_pytorch-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.1 kB
Release files / bitcodes-pytorch-0.0.1.tar.gz
| Download URL | bitcodes-pytorch-0.0.1.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b7f11e9c90b3342af41233a3713abdacdc2c55dc6b0bfe23b6a7c140db33fd88
|
|
BLAKE2b-256 checksum How to use checksums |
ed410eb9eb2ecfba091afc093b549f2e17c6f6c41677162f540db02ededdc74e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Release files / bitcodes_pytorch-0.0.1-py3-none-any.whl
| Download URL | bitcodes_pytorch-0.0.1-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6558a8e6fb6ec2c661a8f8c2f11c4374a226d84e830dddf27294257e15afe233
|
|
BLAKE2b-256 checksum How to use checksums |
e6b008a2f4d513cdd37110874f80f3d1eacdf9975576319529755969f26ad911
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.15
|
Security for bitcodes-pytorch 0.0.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.