aleff
Algebraic effects for Python — deep and shallow, stateful, composable, multi-shot handlers.
from aleff import effect, create_handler
choose = effect("choose")
h = create_handler(choose)
@h.on(choose)
def _(k, *values):
return sum((k(v) for v in values), [])
print(h(lambda: [choose("A", "B") + choose("C", "D")]))
# ['AC', 'AD', 'BC', 'BD']
Features
- Deep handlers — effects propagate through nested function calls without annotation
- Shallow handlers — handle an effect once, then delegate re-installation to the handler function; enables state machines, shift0/reset0, and strategy changes between invocations
- Stateful handlers — handlers can maintain and update state across multiple effect invocations, either via mutable variables (deep) or re-installation with new state (shallow); enables get/put state, transactions, and reverse-mode AD
- Multi-shot continuations —
resumecan be called multiple times in a single handler, enabling backtracking search, non-determinism, and other advanced patterns - Sync and async — both synchronous (
Handler) and asynchronous (AsyncHandler) handlers are supported, with transparent bridging between the two - Effect composition — handler functions can perform effects themselves, dispatched to enclosing handlers; enables layered architectures and modular effect stacking
- Dynamic wind —
windcontext manager establishes before/after guards that are re-invoked on multi-shot re-entry, with optional auto-management of context managers returned bybefore - Effect annotation —
@effect(step1, step2)collects effect sets transitively from decorated functions - Introspection —
effects(fn)andunhandled_effects(fn, h)for querying and validating effect coverage - Typed — effect parameters and return types are checked by type checkers (pyright)
- No macros, no code generation — pure Python library built on greenlet and a small CPython C extension
- Unsafe C-extension boundary —
aleffy()can opt compatible C-extension calls into exact-point native continuation capture on supported builds
Requirements
- CPython >=3.12
- Tested versions:
- 3.12.13
- 3.13.12
- 3.14.3
- 3.14.3t (free-threaded)
- Tested versions:
- greenlet >= 3.3.2
- Linux / macOS / Windows
Installation
# uv
uv add aleff
# pip
pip install aleff
Quick start
from aleff import effect, Effect, Resume, create_handler
# Define effects
read: Effect[[], str] = effect("read")
write: Effect[[str], int] = effect("write")
# Write business logic using effects
def run():
s = read()
return write(s)
# Provide handler implementations
h = create_handler(read, write)
@h.on(read)
def _read(k: Resume[str, int]):
return k("file contents")
@h.on(write)
def _write(k: Resume[int, int], contents: str):
print(f"writing: {contents}")
return k(len(contents))
result = h(run)
print(result) # 13
Multi-shot example
from aleff import effect, Effect, Handler, Resume, create_handler
choose: Effect[[int], int] = effect("choose")
h: Handler[list[int]] = create_handler(choose)
@h.on(choose)
def _choose(k: Resume[int, list[int]], n: int):
# Resume once for each choice and collect all results
results: list[int] = []
for i in range(n):
results += k(i)
return results
def computation():
x = choose(3) # 0, 1, or 2
y = choose(2) # 0 or 1
return [x * 10 + y]
result = h(computation)
print(result) # [0, 1, 10, 11, 20, 21]
Effect composition
Handler functions can perform effects that are handled by enclosing handlers:
from aleff import effect, Effect, Resume, create_handler
log: Effect[[str], None] = effect("log")
parse: Effect[[str], int] = effect("parse")
# Outer handler: logging
h_log = create_handler(log)
@h_log.on(log)
def _log(k: Resume[None, int], msg: str):
print(f"[LOG] {msg}")
return k(None)
# Inner handler: parsing with logging
h_parse = create_handler(parse)
@h_parse.on(parse)
def _parse(k: Resume[int, int], s: str):
log(f"parsing: {s}") # handled by the outer handler
return k(int(s))
result = h_log(lambda: h_parse(lambda: parse("42") + 1))
# prints: [LOG] parsing: 42
print(result) # 43
Dynamic wind
The wind context manager establishes before/after guards around a dynamic extent. When a multi-shot continuation captured inside the with block is resumed, the before thunk is called again; when it exits, the after thunk runs.
from aleff import effect, Effect, Resume, Handler, create_handler, wind
choose: Effect[[], int] = effect("choose")
h: Handler[list[int]] = create_handler(choose)
@h.on(choose)
def _choose(k: Resume[int, list[int]]):
return k(1) + k(2)
log: list[str] = []
def run() -> list[int]:
with wind(lambda: log.append("before"), lambda: log.append("after")):
return [choose() * 10]
result = h(run)
print(result) # [10, 20]
print(log) # ['before', 'after', 'before', 'after']
If before returns a context manager and auto_exit=True (the default), __enter__ and __exit__ are called automatically:
with wind(lambda: open("data.txt")) as ref:
ref.unwrap().read()
# file is closed on exit
wind_range is a multi-shot-safe replacement for range() in for loops. Python's range() iterator is shared across shots and exhausted after the first; wind_range saves and restores the iterator position automatically:
with wind_range(n) as r:
for i in r:
v = choose() # multi-shot safe
How it works
Effects are declared as typed values and invoked like regular function calls. A Handler intercepts these calls via greenlet-based context switching:
- Business logic runs in a greenlet
- When an effect is invoked, control switches to the handler
- The handler processes the effect and calls
resume(value)to return a value - If
resumeis called multiple times, each call restores a snapshot of the continuation's frames (multi-shot) - If the handler returns without calling
resume, the computation is aborted (early exit)
Because handlers use greenlets (not exceptions), the control flow is:
- Transparent — no
yield,await, or special syntax in business logic - Non-stack-cutting — code after
resumein the handler runs after the continuation completes, enabling reverse-order execution (useful for backpropagation, transactions, etc.)
Multi-shot continuations are implemented via a CPython C extension (aleff._multishot.v1._aleff) that snapshots and restores interpreter frame chains.
C-extension boundaries
When an effect is performed while a C-extension call is active, that boundary
must have an Aleff continuation adapter or an explicitly audited aleffy()
wrapper; otherwise Aleff emits CFrameContinuationWarning. See the
Effects & Handlers documentation
for the aleffy() contract.
Package structure
| Package | Description |
|---|---|
aleff |
Default: re-exports aleff.multishot (multi-shot handlers) |
aleff.multishot |
Multi-shot handlers with frame snapshot/restore |
aleff.oneshot |
One-shot handlers (no C extension required) |
Examples
See examples/ for demonstrations:
- N-Queens — backtracking search via multi-shot continuations
- Amb / Logic puzzle — Scheme-style
amboperator and constraint solving (SICP Exercise 4.42) - Probability — exact discrete probability distributions via weighted multi-shot
- Dependency injection — swap DB/email/logging implementations
- Record/Replay — record effect results, replay without side effects
- Transactions — buffer writes, commit on success, rollback on failure
- Automatic differentiation — forward-mode (dual numbers) and reverse-mode (backpropagation) with the same math expressions
- Shallow state machine — mutable state (get/put) and traffic light controller via shallow handler re-installation
- shift/reset, shift0/reset0 — delimited continuations: deep = shift/reset, shallow = shift0/reset0, with generator example
API reference
| Function / Class | Description |
|---|---|
effect("name") |
Create a new Effect |
@effect(e1, e2, ...) |
Decorate a function to declare its effects |
create_handler(*effects, shallow=False) |
Create a synchronous handler |
create_async_handler(*effects, shallow=False) |
Create an asynchronous handler |
h.on(effect) |
Register a handler function (decorator) |
h(caller) |
Run caller with the handler active |
effects(fn) |
Get the declared effect set of a function |
unhandled_effects(fn, *handlers) |
Get effects not covered by the given handlers |
Effect[P, R] |
Effect protocol (parameters P, return type R) |
Handler[V] |
Sync handler protocol |
AsyncHandler[V] |
Async handler protocol |
Resume[R, V] |
Sync continuation (k(value) -> V) |
ResumeAsync[R, V] |
Async continuation (await k(value) -> V) |
wind(before, after, *, auto_exit=True) |
Dynamic wind context manager |
wind_range(stop) / wind_range(start, stop, step) |
Multi-shot-safe range() for for loops |
Ref[T] |
Reference wrapper returned by wind; call unwrap() to get the value |
aleffy(func) |
Opt a compatible C-extension callable into experimental native continuation capture |
CFrameContinuationWarning |
Warning emitted when a snapshot crosses an unsupported C boundary |
enable_c_warnings() / disable_c_warnings() |
Enable or disable C-boundary diagnostics |
c_warnings_enabled() |
Report whether C-boundary diagnostics are active |
Development
From source:
git clone https://github.com/hnmr293/aleff.git
cd aleff
uv sync
# Run tests
uv run pytest
# Run tests on all supported Python versions
./run_tests.sh
# Format
uv run ruff format
# Lint
uv run pyright
License
aleff's original code is licensed under Apache-2.0. Portions of the CPython integration and continuation adapters are derived from CPython and remain subject to PSF-2.0. See LICENSE, NOTICE, and LICENSES/CPython.txt.
Metadata
Release files for aleff 0.5.0
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 |
|---|---|---|---|---|
| aleff-0.5.0.tar.gz | 544.0 kB | With provenance | Details for aleff-0.5.0.tar.gz |
Built distributions (wheels)
Total release size: 18.0 MB
Release files / aleff-0.5.0.tar.gz
| Download URL | aleff-0.5.0.tar.gz |
|---|---|
| Size | 544.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9816a2e401b84648d1a4587ba9065a9aab9cce2dba1d4f992768ba398ff126d3
|
|
BLAKE2b-256 checksum How to use checksums |
ff1f757a56072ebf1cf27b8d9ca444ae13045b52e8b9fbb1835d3864754c16f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314t-win_amd64.whl
| Download URL | aleff-0.5.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 701.0 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
79ec72247bb59ab572545296303949380e5581177ca4f5da4c83b9572632a740
|
|
BLAKE2b-256 checksum How to use checksums |
58687da0f2a71c9e058776485f57543eb8e1c5c0f4607b8c70583d3af1ae55dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aleff-0.5.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.9 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
2cd41bfa1551eba023b7b441e10ddcee864d373cc256be65627d7dbf4b1561d2
|
|
BLAKE2b-256 checksum How to use checksums |
9ac2d472cc89ef5383b036e62a3131422522bb60ab785ef36b03818ef32c3b0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | aleff-0.5.0-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 691.6 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1a35b18a0873d655864a2a120419468b021d761f08a904c44672ea43544e1c2b
|
|
BLAKE2b-256 checksum How to use checksums |
c2740d6ca197c04204a0343b1be932aeb36b6db9aad3649d98c48efafd900348
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314t-macosx_10_15_x86_64.whl
| Download URL | aleff-0.5.0-cp314-cp314t-macosx_10_15_x86_64.whl |
|---|---|
| Size | 699.5 kB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
15de7dc2944ae178c67bc81f5114a9823db316607838bb5e38b1eb18d682b7c1
|
|
BLAKE2b-256 checksum How to use checksums |
32661caf0771028060c63179b5e78c2ca25e8c90a87943dc7aeeac302ca074f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314-win_amd64.whl
| Download URL | aleff-0.5.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 677.2 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5ef976db3eef0b15ec989d102f76285e3fb8a9cbae1e910f87a2e1688920d2cd
|
|
BLAKE2b-256 checksum How to use checksums |
88d6b69e1ecef007236554be24498105d8af2922e658cbffc289a45917f86704
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aleff-0.5.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
1ed9e43e6ce5ac3547e16de286783cfe47650445fa002ba72b8158cf3b4c285e
|
|
BLAKE2b-256 checksum How to use checksums |
4ec48aa3f447efccf1299a9c780dd4effc55c8dc49e4a70000dc9bfd70747963
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | aleff-0.5.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 652.6 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
49497e7d28cfb5b00f6a59a5540701d0af4c7dec8cf3de0ad8f3e87814b84a35
|
|
BLAKE2b-256 checksum How to use checksums |
c5b1de049b64d88bb8d11ca1dbf2235f2e95e97a131af8a9a220abf700221257
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | aleff-0.5.0-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 663.3 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
9b384c9fc958d1fcf36e59cf7394b56cfe38a52db894b78638fd88f7404f4b9d
|
|
BLAKE2b-256 checksum How to use checksums |
5c970ffbba89812a09fe83ba528e46a45518cd665679a6a7f46b0b13965386ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp313-cp313-win_amd64.whl
| Download URL | aleff-0.5.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 669.9 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
37bda2f2bc66d97aff70b80198f20ca71b8d95b7b82ce17343fb74affa1abc20
|
|
BLAKE2b-256 checksum How to use checksums |
83259dae56c8cd5c765560e8e0027924dfedab7a64c0a52f494bdf7aa7d8a9b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aleff-0.5.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9a935ee2f8134f90f52bc268a2f0a8b1275e43c23b411226ab3615407f5a3818
|
|
BLAKE2b-256 checksum How to use checksums |
1a45da6aeaa1a768939b6a0803ea55d3a33b4e9842a8eae4416b0d8ba70d3169
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | aleff-0.5.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 648.6 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6ebc6cdfd29377228c0cb659afd51045d7ee1821df44f153aafee48e91a082e3
|
|
BLAKE2b-256 checksum How to use checksums |
9ea4a7052483b7b6d03724a1dd83ec41c1c635d3c2eff1758f034331c348e37f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | aleff-0.5.0-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 659.2 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
5f7c6792ce0a8c1961b5a98f84e7150f8291e6827e39c2c50c35acad757d89e6
|
|
BLAKE2b-256 checksum How to use checksums |
b1d02c881eda60fa036a8b782f6459be6d45adfb7c31cb67add1d5b3b9fae0a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp312-cp312-win_amd64.whl
| Download URL | aleff-0.5.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 669.5 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
fb04fc3c2a03c610c8a4b098393a487ec55326b60d0dc5e95ce5a6f00101f21f
|
|
BLAKE2b-256 checksum How to use checksums |
e839c5332acf216dfdb542b7a969b82187b30eda70969948583bbba940828cd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | aleff-0.5.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
bff1fe92a6b92ddb5aa17c1ce4e641d564573d91e953852dfab7162676c5c781
|
|
BLAKE2b-256 checksum How to use checksums |
652d95ea33dc6ecb53e0c5c076324ddc94f08de9c0f6217a3926e838dd066f59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | aleff-0.5.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 643.9 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6a5abd9dd32de7b58eb5b5868f7af1e8510c098e6120a1f5a328f6dc6cca3fc4
|
|
BLAKE2b-256 checksum How to use checksums |
9ca8009b4358e7544f7d309a10643df663c11bc0e74cc9391127933ffef792ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logRelease files / aleff-0.5.0-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | aleff-0.5.0-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 654.8 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
73d249aaf66e284e9fdc12361780759fa656b3d96d44abb61e51ecf722930903
|
|
BLAKE2b-256 checksum How to use checksums |
a3bc29e3508c9b1f4df9cd749ab629141ba2e9026c2a0b14184257e5b90516fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 5, 2026.
Transparency logSecurity for aleff 0.5.0
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 17 files in this release have been uploaded with provenance metadata.
Attestation for aleff-0.5.0.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 Sep 5, 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.