Release files for asyncio-bidirection-rpc 24.2.2
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 | |
|---|---|---|---|---|
| asyncio-bidirection-rpc-24.2.2.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyncio_bidirection_rpc-24.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.7 kB
Release files / asyncio-bidirection-rpc-24.2.2.tar.gz
| Download URL | asyncio-bidirection-rpc-24.2.2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d246fd89518d82490106adfa799fb5bf989d3d4d582c66f27bfafdc7f96bb9f9
|
|
BLAKE2b-256 checksum How to use checksums |
c6f5099315263d7a0e9533f0fe948f831904a45ff132341349cbb8113ac5e5ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / asyncio_bidirection_rpc-24.2.2-py3-none-any.whl
| Download URL | asyncio_bidirection_rpc-24.2.2-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1590d4846caa950dada0950e1d454b2a532e6f11945eb02e9da2355ab074766
|
|
BLAKE2b-256 checksum How to use checksums |
8e472180ee495c88c472f339cf45287c52f2f64cf4305bfa5f27d2ca453f4696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for asyncio-bidirection-rpc 24.2.2
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.
