aiter -- Asynchronous Iterator Patterns
PEP 525 describes asynchronous iterators, a merging of iterators with async functionality. Python 3.6 makes legal constructs such as
async for event in peer.event_iterator:
await process_event(event)
which is a huge improvement over using async.Queue objects which have no built-in way to determine "end-of-stream" conditions.
This module implements some patterns useful for python asynchronous iterators.
Documentation available on readthedocs.io.
A tutorial is available. github version
CAVEAT This project is still in its infancy, and I reserve the right to rename things and cause other breaking changes.
Metadata
Release files for aiter 0.13.20191203
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 |
|---|---|---|---|---|
| aiter-0.13.20191203.tar.gz | 9.3 kB | Without provenance | Details for aiter-0.13.20191203.tar.gz |
Release files / aiter-0.13.20191203.tar.gz
| Download URL | aiter-0.13.20191203.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b99a5dcdceccc8f2c2c10b1327d462353f7ab1aedc8ae17fcd3d2331db5ff429
|
|
BLAKE2b-256 checksum How to use checksums |
4cc5efb9abdb6b4e85bb0ff0b3c2e066e813de64db18a23789c22e638a019087
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.40.0 CPython/3.7.5
|
Security for aiter 0.13.20191203
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.