Skip to main content

requ

Explicit, bounded HTTP(S) requests with Python's standard library. Python 3.14+; no runtime dependencies.

pip install requ
from requ import Client

with Client(timeout=10, max_bytes=2_000_000, max_connections=4) as client:
    response = client.post('https://api.example.com/users', json={'name': 'Ash'})
    response.raise_for_status()
    user = response.json()

Use AsyncClient with async with and await client.request(...) for asynchronous applications. Its I/O runs in worker threads. Canceling an await does not undo or stop a dispatched request; the connection remains leased until the worker returns.

  • General methods, query pairs, bounded bytes/finite JSON and owned responses.
  • Client-owned HTTP/1.1 pool with finite capacity, lease wait and idle expiry.
  • Verified TLS, validated headers, strict framing and bounded redirects.
  • No retries, cookies, automatic decompression or global opener changes.
  • Environment proxies require trust_env=True; proxy requests use non-pooled urllib transport while retaining the client's concurrency/body/socket bounds.

timeout bounds individual blocking socket operations. It is not a DNS or total wall-clock deadline. Direct sockets remain in the pool until expiry or close(); responses themselves contain only owned bytes. Always use a context or close the client when finished. GET/HEAD may follow bounded redirects; mutations return their redirect response without replay. Cross-origin redirect opt-in strips caller headers.

See the API reference for the precise limits and error contract. API resources, credentials and GraphQL belong in a higher-level library such as apiconn.

Development: uv sync, then uv run python -W error::ResourceWarning -m unittest discover -s tests -v. Build and independently test both distributions with uv run python scripts/check_distribution.py.

MIT.

Metadata

Release files for requ 0.1.0

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

Source distribution (sdist)

Source distribution for requ 0.1.0
File Size Uploaded Provenance Actions
requ-0.1.0.tar.gz 20.6 kB With provenance Details for requ-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for requ 0.1.0
File Interpreter ABI Platform Actions
requ-0.1.0-py3-none-any.whl Python 3 none any Details for requ-0.1.0-py3-none-any.whl

Total release size: 30.4 kB

Release files / requ-0.1.0.tar.gz

Download URL requ-0.1.0.tar.gz
Size 20.6 kB
Tags Source
SHA-256 checksum
How to use checksums
8d213f19be1f7391a4858a94678eaa78a5ccec4a7ca068e3ece0e52f6b3d36a7
BLAKE2b-256 checksum
How to use checksums
297f8f4c66deec49c301a3747bddf7836d98411134fe277fbca8dc846ee47eb6
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 Nov 8, 2026.

Transparency log

Release files / requ-0.1.0-py3-none-any.whl

Download URL requ-0.1.0-py3-none-any.whl
Size 9.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dc348f6f3f50b74fb020ee2804b3e668f0ef488bf1673b468c5110ab232d3ebe
BLAKE2b-256 checksum
How to use checksums
aeffce12febb0c424342a6378f1b9e3601ff70a526e23c9929c130dbd3f37128
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 Nov 8, 2026.

Transparency log

Security for requ 0.1.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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for requ-0.1.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 Nov 8, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

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