Fork of original eosapi with significant improvements:
- Complete rework of async implementation
- Modern Python versions support
- Enhanced error handling
- Performance optimizations including shared HTTP session
- Updated documentation
- Fixed RIPEMD160 compatibility issues
Original code by encoderlee (encoderlee@gmail.com)
Metadata
Release files for eosapi-async 2.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 | Actions |
|---|---|---|---|---|
| eosapi_async-2.2.2.tar.gz | 22.4 kB | Without provenance | Details for eosapi_async-2.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eosapi_async-2.2.2-py3-none-any.whl | Python 3 | none | any | Details for eosapi_async-2.2.2-py3-none-any.whl |
Total release size: 38.9 kB
Release files / eosapi_async-2.2.2.tar.gz
| Download URL | eosapi_async-2.2.2.tar.gz |
|---|---|
| Size | 22.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
937cd2fd2543f6c4c4bdcf5fdf93ee54327d92349564bb0363988fe409c9ec64
|
|
BLAKE2b-256 checksum How to use checksums |
2c4e6176905eb0edae50ef4aff3a41620e997f7273d51b717f294020b2083862
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Release files / eosapi_async-2.2.2-py3-none-any.whl
| Download URL | eosapi_async-2.2.2-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
288db9935d5ae49fe86daea323ef371d3bcff7b8924a4afb0ead7cac6f5ed6e5
|
|
BLAKE2b-256 checksum How to use checksums |
0075f33c26cc206a6f0f7e9545a62630592bfd03bbc64841b82889598149e32c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.4
|
Security for eosapi-async 2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.