aiolimiter
Introduction
An efficient implementation of a rate limiter for asyncio.
This project implements the Leaky bucket algorithm, giving you precise control over the rate a code section can be entered:
from aiolimiter import AsyncLimiter
# allow for 100 concurrent entries within a 30 second window
rate_limit = AsyncLimiter(100, 30)
async def some_coroutine():
async with rate_limit:
# this section is *at most* going to entered 100 times
# in a 30 second period.
await do_something()
It was first developed as an answer on Stack Overflow.
Documentation
https://aiolimiter.readthedocs.io
Installation
$ pip install aiolimiter
The library requires Python 3.10 or newer.
Requirements
- Python >= 3.10
License
aiolimiter is offered under the MIT license.
Source code
The project is hosted on GitHub.
Please file an issue in the bug tracker if you have found a bug or have some suggestions to improve the library.
Developer setup
This project uses uv to manage dependencies, testing and releases. Make sure you have installed that tool, then run the following command to get set up:
uv sync
Tests are run with pytest and tox. Releases are made managed by a GitHub Actions workflow. Code quality is maintained with ruff and pyright, and prek runs quick checks to maintain the standards set.
A Taskfile is provided that defines specific tasks such as linting, formatting or previewing the documentation:
$ task --list
task: Available tasks for this project:
* default: Default task, runs linters and tests
* dev:format: Runs formatters (aliases: format)
* dev:install-prek: Install prek into local git checkout (aliases: dev:install-precommit)
* dev:lint: Runs linters (aliases: lint)
* dev:lint:code: Lint the source code
* dev:lint:renovate: Lint the Renovate configuration file
* dev:test: Run tests (aliases: test)
* dev:tox: Run tests with tox (aliases: tox)
* dev:uv-lock: Updates the uv lock file (aliases: lock)
* dist:build: Build the distribution packages (aliases: dist)
* dist:clean: Remove built distribution packages (aliases: clean)
* dist:publish: Publish package to PyPI (aliases: publish)
* docs:build: Build project documentation (aliases: docs)
* docs:checks: Run all documentation checks
* docs:checks:spelling: Check documentation spelling.
* docs:checks:towncrier: Check changelog towncrier output()
* docs:checks:towncrier_fragments: Check changelog towncrier fragments
* docs:clean: Clean the documentation build directory
* docs:serve: Live preview server for project documentation (aliases: preview)
Release files for aiolimiter 1.3.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 | |
|---|---|---|---|
| aiolimiter-1.3.0.tar.gz | 10.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiolimiter-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / aiolimiter-1.3.0.tar.gz
| Download URL | aiolimiter-1.3.0.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7343008c2228e89def7d4ce29ab98ee98822bf5db69018c09c90088929f7c104
|
|
BLAKE2b-256 checksum How to use checksums |
26600d16f90083a2f0ae9421d11ad98287f7942414f091ae9ad318389a764f85
|
| 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 7, 2026.
Transparency logRelease files / aiolimiter-1.3.0-py3-none-any.whl
| Download URL | aiolimiter-1.3.0-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0c16c377049fb2e40cc3373770e29c063de32aa25d84e5db168c854da6462b7
|
|
BLAKE2b-256 checksum How to use checksums |
56d89237b1d29e561bd37ffe9487ea1a4551d2df2902d9b79a6ea6b18e4fcc73
|
| 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 7, 2026.
Transparency log