This release is a pre-release and may not be stable for production use.
PyRill
Asynchronous streams for Python.
PyRill builds asynchronous data pipelines in plain Python. You connect small
elements (sources, stages and sinks) with >>, and the data flows through them one
frame at a time, on top of asyncio and with no dependencies.
import asyncio
from pyrill.accumulators import ListAcc
from pyrill.mappers import Map
from pyrill.sinks import Last
from pyrill.sources import IterableSource
async def main() -> None:
pipeline = (
IterableSource(source=["alpha", "beta", "gamma"])
>> Map(map_func=str.upper)
>> ListAcc()
>> Last()
)
print(await pipeline.get_frame())
asyncio.run(main())
['ALPHA', 'BETA', 'GAMMA']
Why PyRill
Programs that handle streams (files, sockets, API responses, queues) tend to grow hand-written loops that mix reading, parsing, filtering, timing and error handling. PyRill turns each of those concerns into a small, typed, reusable element that you can test alone and connect with the others.
- Pull-based. Work happens only when a frame is needed, so a slow consumer slows the whole pipeline, and frames do not pile up in memory unless you add a buffer.
- Streaming. A pipeline works on one frame at a time, so memory use depends on the size of the frames, not on the length of the stream.
- Batteries included. Elements for files and asyncio streams, byte and text
re-chunking, safe UTF-8 decoding, CSV, JSON, branching (
Tee), pairing (Zip), merging (Union), timeouts and deadlines, pausing (Gate), buffering (Queue) and more. - Extensible. Write your own sources, stages and sinks, or package a chain of stages as a single reusable stage.
- Typed. Elements are generic classes, so type checkers follow the frames through a pipeline.
Installation
PyRill needs Python 3.14 or later and has no other dependencies.
$ pip install pyrill
To work on PyRill itself, clone the repository, run uv sync, and run the tests with
uv run pytest.
Documentation
Full documentation, including a quickstart, the core concepts, task-oriented guides
and a catalog of every element, is at
https://pyrill-framework.readthedocs.io/stable/. The same pages are in the
docs/ folder.
Project
- Repository and issue tracker: https://github.com/pyrill-framework/pyrill
- License: LGPL-2.1-or-later
Metadata
Release files for pyrill 0.2.0b0
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 |
|---|---|---|---|---|
| pyrill-0.2.0b0.tar.gz | 59.0 kB | With provenance | Details for pyrill-0.2.0b0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyrill-0.2.0b0-py3-none-any.whl | Python 3 | none | any | Details for pyrill-0.2.0b0-py3-none-any.whl |
Total release size: 126.4 kB
Release files / pyrill-0.2.0b0.tar.gz
| Download URL | pyrill-0.2.0b0.tar.gz |
|---|---|
| Size | 59.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1f57aeb3e524a9b4cfc2b27775158707694c65439f0d9ddf08db21a78ad10d1
|
|
BLAKE2b-256 checksum How to use checksums |
e600ce06f6f967b9841adcebca828c8a5a8b5fbc9c613fc40a9d14050e7b742d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / pyrill-0.2.0b0-py3-none-any.whl
| Download URL | pyrill-0.2.0b0-py3-none-any.whl |
|---|---|
| Size | 67.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebcd105c196dfcfc946cc4ecc35eb7ce2f985b53d344758b4a0f452fa4f13cd9
|
|
BLAKE2b-256 checksum How to use checksums |
27b2a03ac4eeed04bd918f4dd98bf233d7307d45eb51d17837b73f256e48d55a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for pyrill 0.2.0b0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pyrill-0.2.0b0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA 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.