Skip to main content

Pyper

Concurrent Python made simple

Test Coverage Package version Supported Python versions


Pyper is a flexible framework for concurrent and parallel data-processing, based on functional programming patterns. Used for 🔀 ETL Systems, ⚙️ Data Microservices, and 🌐 Data Collection

See the Documentation

Key features:

  • 💡Intuitive API: Easy to learn, easy to think about. Implements clean abstractions to seamlessly unify threaded, multiprocessed, and asynchronous work.
  • 🚀 Functional Paradigm: Python functions are the building blocks of data pipelines. Let's you write clean, reusable code naturally.
  • 🛡️ Safety: Hides the heavy lifting of underlying task execution and resource clean-up. No more worrying about race conditions, memory leaks, or thread-level error handling.
  • ⚡ Efficiency: Designed from the ground up for lazy execution, using queues, workers, and generators.
  • ✨ Pure Python: Lightweight, with zero sub-dependencies.

Installation

Install the latest version using pip:

$ pip install python-pyper

Note that python-pyper is the pypi registered package.

Usage

In Pyper, the task decorator is used to transform functions into composable pipelines.

Let's simulate a pipeline that performs a series of transformations on some data.

import asyncio
import time

from pyper import task


def get_data(limit: int):
    for i in range(limit):
        yield i


async def step1(data: int):
    await asyncio.sleep(1)
    print("Finished async wait", data)
    return data


def step2(data: int):
    time.sleep(1)
    print("Finished sync wait", data)
    return data


def step3(data: int):
    for i in range(10_000_000):
        _ = i*i
    print("Finished heavy computation", data)
    return data


async def main():
    # Define a pipeline of tasks using `pyper.task`
    pipeline = task(get_data, branch=True) \
        | task(step1, workers=20) \
        | task(step2, workers=20) \
        | task(step3, workers=20, multiprocess=True)

    # Call the pipeline
    total = 0
    async for output in pipeline(limit=20):
        total += output
    print("Total:", total)


if __name__ == "__main__":
    asyncio.run(main())

Pyper provides an elegant abstraction of the execution of each task, allowing you to focus on building out the logical functions of your program. In the main function:

  • pipeline defines a function; this takes the parameters of its first task (get_data) and yields each output from its last task (step3)
  • Tasks are piped together using the | operator (motivated by Unix's pipe operator) as a syntactic representation of passing inputs/outputs between tasks.

In the pipeline, we are executing three different types of work:

  • task(step1, workers=20) spins up 20 asyncio.Tasks to handle asynchronous IO-bound work

  • task(step2, workers=20) spins up 20 threads to handle synchronous IO-bound work

  • task(step3, workers=20, multiprocess=True) spins up 20 processes to handle synchronous CPU-bound work

task acts as one intuitive API for unifying the execution of each different type of function.

Each task has workers that submit outputs to the next task within the pipeline via queue-based data structures; this is the mechanism underpinning how concurrency and parallelism are achieved. See the docs for a breakdown of what a pipeline looks like under the hood.


See a non-async example

Pyper pipelines are by default non-async, as long as their tasks are defined as synchronous functions. For example:

import time

from pyper import task


def get_data(limit: int):
    for i in range(limit):
        yield i

def step1(data: int):
    time.sleep(1)
    print("Finished sync wait", data)
    return data

def step2(data: int):
    for i in range(10_000_000):
        _ = i*i
    print("Finished heavy computation", data)
    return data


def main():
    pipeline = task(get_data, branch=True) \
        | task(step1, workers=20) \
        | task(step2, workers=20, multiprocess=True)
    total = 0
    for output in pipeline(limit=20):
        total += output
    print("Total:", total)


if __name__ == "__main__":
    main()

A pipeline consisting of at least one asynchronous function becomes an AsyncPipeline, which exposes the same usage API, provided async and await syntax in the obvious places. This makes it effortless to combine synchronously defined and asynchronously defined functions where need be.

Examples

To explore more of Pyper's features, see some further examples

Dependencies

Pyper is implemented in pure Python, with no sub-dependencies. It is built on top of the well-established built-in Python modules:

License

This project is licensed under the terms of the MIT license.

Release files for python-pyper 0.4.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for python-pyper 0.4.4
File Size Uploaded
python_pyper-0.4.4.tar.gz 349.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for python-pyper 0.4.4
File Interpreter ABI Platform
python_pyper-0.4.4-py3-none-any.whl Python 3 none any Details

Total release size: 367.3 kB

Release files / python_pyper-0.4.4.tar.gz

Download URL python_pyper-0.4.4.tar.gz
Size 349.0 kB
Tags Source
SHA-256 checksum
How to use checksums
fbf9f4f5f95f8263a608770424f11558a07896a3d1b1a2699e4ba295b5100f7b
BLAKE2b-256 checksum
How to use checksums
18bc7e67eff590248554dfb4e325a979ccfa188c80259923cd3d255c4ac291c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Jan 20, 2025.

Transparency log

Release files / python_pyper-0.4.4-py3-none-any.whl

Download URL python_pyper-0.4.4-py3-none-any.whl
Size 18.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f324cb2bdd0ee4153a0fb7d6011d54c12a9ea2dd3b74fd01652bcc067774ffe8
BLAKE2b-256 checksum
How to use checksums
9bd2f8ebc2d7e1cd48403a8e9aa0855739c97e0fdd007448582c0dc2ca7a3915
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Jan 20, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.4 This release

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.2.1

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page