Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

httpperf

An asyncio HTTP client for load testing, built on libcurl.

Design

A load-testing client has three jobs: drive as much load as possible from each machine, report the server's response times rather than time spent waiting on the client, and read responses promptly so the server never sees a slow reader. httpperf is built around these.

All network I/O runs in a small C event loop (the vendored ae reactor from Redis) on its own thread, which never takes the GIL. Python hands requests to that thread and collects finished responses through pipes:

asyncio loop ──req_in pipe──▶ curl thread (ae + curl multi) ──▶ sockets
     ▲                               │
     └──────── req_out pipe ◀────────┘

Bytes are read off the wire as they arrive, whatever Python is doing. If Python falls behind, finished responses wait in the pipe rather than in socket buffers, so the client simply sends new requests more slowly, and curl's timings stay accurate. The cost is the hand-off itself, and the curl thread uses roughly one extra core under load. That is deliberate: a spare core is cheap, and response times you can't trust are worthless.

Response.client_lag shows how far Python is behind (see Timings).

Install

pip install httpperf

Wheels are published for Linux on x86_64 and aarch64, for Python 3.9 to 3.15, with glibc 2.34 or later (Ubuntu 22.04, Debian 12, RHEL 9 and later) or musl (Alpine). They include their own libcurl, with HTTP/2 and HTTP/3.

Anywhere else, including Python 3.8, pip builds from source against the system's libcurl, which needs its development headers and a C compiler. That libcurl decides whether HTTP/3 is available: curl -V lists HTTP3 under Features when it does.

sudo apt install libcurl4-openssl-dev   # Debian/Ubuntu
pip install httpperf

To build against your own libcurl even where a wheel exists, skip the wheel, point the build at it and make sure it is found at run time:

CFLAGS=-I$PREFIX/include LDFLAGS="-L$PREFIX/lib -Wl,-rpath,$PREFIX/lib" pip install --no-binary httpperf httpperf

A session with http_version="HTTP/3" raises ValueError if the libcurl in use lacks HTTP/3.

Quick start

import asyncio

import httpperf


async def main():
    async with httpperf.Session() as session:
        r = await session.get("https://example.com/")
        print(r.status_code, r.http_version, r.total_time, r.client_lag)


asyncio.run(main())

Sessions are cheap: create one per virtual user or journey. They share a default Engine (the curl thread, the shared connection pool and the TLS cache) unless you pass your own.

API

Session(*, engine=None, ...)

All arguments are keyword-only. A session can be created anywhere, even outside a running asyncio loop.

Argument Default Meaning
engine None The Engine to use. None means the default engine of the asyncio loop the session is first used in, created when first needed and shared by every session in that loop without one.
connections "shared" "shared": the engine's pool. "session": the session's own pool. "none": a new connection for every request.
tls "shared" Where TLS session tickets are kept. "shared": in the engine, so new connections resume their handshake. "session": per session, so each session starts with a full handshake.
http_version "HTTP/2" "HTTP/2": HTTP/2 over TLS when the server offers it, with requests waiting to share one multiplexed connection. Plain http uses HTTP/1.1. "HTTP/1.1": HTTP/1.1 only. "HTTP/3": HTTP/3 over QUIC only, with no fallback, so requests fail if the server does not offer it.
idle_timeout 118 Seconds a connection may sit idle and still be reused.
max_connection_age 0 Seconds after which a connection is no longer reused, however busy it is. 0 means no limit.
max_host_connections 0 Per-session cap on connections per host. Needs connections="session" or "none".
max_connections 0 Per-session cap on connections in use. Needs connections="session" or "none".
cert None (certfile, keyfile) paths for a client certificate, used by every request unless the request overrides it.
timeout None Seconds allowed for each request, from the start of the transfer to the last byte (each redirect hop separately). None or 0 means no limit. Cancelling the task (or asyncio.wait_for) also stops the transfer and frees its connection slot; on HTTP/1.1 that closes the connection, on HTTP/2 and HTTP/3 it resets only that stream.
connect_timeout None Seconds allowed to connect, TLS included. None means curl's default of 300 s.
verify False Server certificate checking. False: none, as most load tests want. True: check against the system CA bundle: SSL_CERT_FILE if set, otherwise libcurl's own default, or the usual system locations if it has none. A path: check against that CA bundle. Requests can override it.
json_dumps None Function that turns a json= argument into the request body (str or bytes). None means the engine's.
json_loads None Function that turns the response body (bytes) into the result of json(). None means the engine's.

Proxies come from the environment, as curl reads them: http_proxy (not HTTP_PROXY, which curl ignores for security), https_proxy or HTTPS_PROXY, then all_proxy or ALL_PROXY, with no_proxy or NO_PROXY for exceptions. A session reads them once, when it is created, so later changes apply to new sessions only.

Cookies always belong to the session, whatever the connection settings.

Engine(*, max_host_connections=0, max_total_connections=0, max_idle_connections=1000, json_dumps=..., json_loads=...)

What sessions share: the curl thread, the shared connection pool, the TLS session cache and the limits. Most programs never create one. Create one to set limits, or to keep groups of sessions in separate pools, and pass it to Session(engine=...).

Argument Meaning
max_host_connections Cap on connections per host for the engine's sessions that use the shared pool or no pool. 0 means no limit. httpperf queues requests above it and reports the wait as queue_time.
max_total_connections Cap on all connections for the same sessions. 0 means no limit.
max_idle_connections How many connections each pool keeps (the shared pool, and each session's own pool). Must be at least 1.
json_dumps, json_loads The JSON functions for the engine's sessions, unless a session sets its own. The defaults use the standard library: compact output, and bodies decoded as UTF-8. See JSON.

Each asyncio loop has its own default engine, so sessions without an engine work in any thread, and in each asyncio.run(), without setup. A loop's default engine lasts as long as the loop, and is closed once the loop has been closed and no session uses it.

An engine binds to the asyncio loop running when it is first used, and so does a session. An engine serves one loop at a time, and using it from a second live loop raises RuntimeError. Once its loop is closed, as at the end of asyncio.run(), it binds to the next one and keeps its pool. So a session kept between asyncio.run() calls keeps its connections. To run loops in several threads at once with your own engines, give each thread its own Engine.

engine.close() stops the curl thread and closes the shared pool's connections, and later requests raise RuntimeError. Requests still in flight fail with RequestError, and a ResourceWarning says how many there were. with and async with call close() on exit. An engine that is no longer referenced is closed automatically. See docs/connections.md for how these fit together.

Session methods

  • await session.get(url, **kwargs), and likewise post, put, patch, delete, head and options.
  • await session.request(method, url, **kwargs).
  • session.close(): closes the session's connections once its requests finish. Later requests raise RuntimeError. with and async with call it on exit.
  • session.cookies(): the cookie jar as a dict.
  • session.get_cookie_list(), session.add_cookie_list(cookies), session.erase_all_cookies() and session.erase_session_cookies(): work with Cookie objects. These are ordinary methods, not coroutines.
  • session.set_response_callback(callback): called with each Response, including each hop of a redirect.

Request arguments

Argument Meaning
params Query parameters: a dict or list of pairs (lists as values repeat the key), or a ready-made string. Added to any query already in the URL.
headers Dict of headers.
headers_list List of "Name: value" strings, for repeated headers.
cookies Dict of cookies to send with this request (added to the session jar).
cookie_list List of Cookie objects.
auth (username, password) for basic auth.
data Request body: str or bytes as is, with no Content-Type unless you set one, or a dict or list of pairs, form-encoded with Content-Type: application/x-www-form-urlencoded unless you set it.
json Object to send as JSON, encoded with the session's json_dumps. Sets Content-Type: application/json unless you set it.
files Dict (or list of pairs) of files to send as multipart/form-data, with any data dict as extra fields. A value is an open file, or (filename, content) or (filename, content, content_type), where content is bytes, str or a file. Files are read into memory.
cert (certfile, keyfile), overriding the session's certificate.
verify True, False or a CA bundle path, overriding the session's verify.
timeout, connect_timeout Override the session's. timeout=0 removes the session's limit for this request.
allow_redirects Follow redirects (default True; False for head).
max_redirects Default 5. Raises RequestError("Max Redirects") beyond it.

Failed transfers raise httpperf.RequestError with curl's detailed error message, such as Failed to connect to 127.0.0.1 port 8080 after 0 ms: Couldn't connect to server. Its code is curl's error code. Timeouts raise httpperf.Timeout, a subclass, so they can be counted separately.

Response

Attribute Meaning
status_code HTTP status.
ok True if the status is below 400.
reason Reason phrase from the status line, or the standard phrase for HTTP/2 and HTTP/3, which send none.
raise_for_status() Raises httpperf.HTTPError (a RequestError, with the response) for 4xx and 5xx statuses.
elapsed total_time as a timedelta.
url Effective URL.
redirect_url Location of a redirect, or None.
history Earlier responses in a redirect chain.
http_version "HTTP/1.0", "HTTP/1.1", "HTTP/2" or "HTTP/3".
headers Case-insensitive mapping of the response headers. Repeated headers are joined with , , as in requests. headers_tuple keeps repeats and order. Both skip interim responses such as 100 Continue. header is the raw text of every header block, decoded as latin-1.
body Bytes.
text Body decoded with encoding.
encoding From the Content-Type charset, else latin-1 (utf-8 for JSON). Can be set.
json() Body parsed with the session's json_loads, once. By default the standard library, always as UTF-8, as RFC 8259 requires.
cookies, cookielist The cookies this response set, from its Set-Cookie headers, as a dict or as Cookie objects. The session's whole jar is session.cookies().
primary_ip Address connected to.
upload_size, download_size Bytes, as integers.
request The Request: method, url, headers, cookies, auth, data.

JSON

By default httpperf uses the standard library's json: compact output for json=, and response bodies decoded as UTF-8 for json(). It needs no extra dependency and has the most scrutinised parser, which matters because load tests often fetch responses from third parties.

If JSON costs too much CPU, pass faster functions as json_dumps and json_loads, on the Engine for all its sessions or on one Session. orjson is a good choice for encoding, and pysimdjson for decoding. Create the parser once, at module scope, since it keeps its buffers between documents:

import httpperf
import orjson
import simdjson

parser = simdjson.Parser()
engine = httpperf.Engine(json_dumps=orjson.dumps, json_loads=parser.parse)


async def journey():
    async with httpperf.Session(engine=engine) as session:
        r = await session.post("https://example.com/search", json={"q": "httpperf"})
        return r.json()["items"][3]["name"]

Things to know:

  • orjson is about 8 times faster than json on larger payloads, but turns NaN into null and refuses integers over 64 bits.
  • parser.parse is lazy: only the values you touch become Python objects. That was about 8 times faster than json.loads for reading one field of a 500 KB document. The result is read-only and not a real dict or list; .as_dict() and .as_list() convert it. Documents stay valid after the parser moves on to the next one.
  • To get real dicts and lists from simdjson, use json_loads=lambda body: parser.parse(body, True).
  • Request bodies that never change can be encoded once and sent as data=, with headers={"Content-Type": "application/json"}.

Timings

All in seconds.

Attribute Meaning
start_time, end_time Wall-clock times (time.time()) when the request was made and when Python received the response.
namelookup_time DNS, measured by curl from the start of the transfer.
connect_time TCP connect complete. 0 when the connection was reused.
appconnect_time TLS handshake complete. 0 for plain http and reused connections.
pretransfer_time Ready to send.
posttransfer_time Request fully sent. starttransfer_time − posttransfer_time is the server's time to first byte, without connection setup or upload. None with libcurl older than 8.10.
starttransfer_time First byte received.
total_time Transfer complete.
queue_time Time waiting in httpperf's queue for a connection, under the engine or session limits. 0 if the request did not wait. curl's timings start after it.
client_lag end_time − start_time − total_time − queue_time: time the request spent waiting on Python, before it was sent and after it finished. Measured with the monotonic clock, so clock changes don't affect it.

curl measures its timings on the curl thread, so a busy Python process does not inflate them. client_lag is how you see that Python is the bottleneck: if it grows, the client cannot keep up, and achieved request rates describe the client rather than the server. Report it alongside response times (p50, p99, max).

queue_time is real waiting that a user would see (a browser's "stalled" time), but it is client-side, so keep it out of server latency.

Known limitations

  • curl closes expired idle connections lazily, the next time the pool needs a connection, so the server sees the close late. See docs/connections.md.
  • Requests in flight when Engine.close() is called never complete.

Development

make test
make lint               # ruff and clang-format, check only
make lint-fix           # apply formatting and fixes
make clean              # remove build output, caches and profiler output (keeps .venv)
make distclean          # also remove .venv

Each target first creates .venv with uv, if needed, and installs httpperf in editable mode with the dev tools. It reinstalls when setup.py, pyproject.toml or the C sources change, so C edits are rebuilt automatically. make venv does only that step.

make venv PY_VERSION=3.8 VENV=.venv-3.8 builds another venv, and VENV=.venv-3.8 on make test or make lint uses it.

To release, set __version__ in httpperf/version.py (for example 1.0rc1 or 1.0), commit and push to main, then run make release. It tags v<version> and pushes the tag, and the release workflow builds the wheels and publishes them to PyPI.

The tests run local servers: pytest-httpbin, small threaded http.server servers for connection counting and TLS, and hypercorn for HTTP/2 and HTTP/3 (skipped on Python 3.8, where hypercorn's HTTP/3 server hangs on shutdown). Client certificates are generated with openssl. The httpbin server is single-threaded, so keep concurrency in tests low.

Set HTTPPERF_PROFILE=1 when building to instrument the extension. See docs/profiling.md.

Licence

MIT. See LICENSE. NOTICE covers the bundled Redis event library and the libraries included in the binary wheels.

Metadata

Release files for httpperf 1.0rc3

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

Source distribution (sdist)

Source distribution for httpperf 1.0rc3
File Size Uploaded Provenance Actions
httpperf-1.0rc3.tar.gz 69.3 kB With provenance Details for httpperf-1.0rc3.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for httpperf 1.0rc3
File Actions
httpperf-1.0rc3-cp315-cp315-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp315-cp315-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp315-cp315-musllinux_1_2_aarch64.whl CPython 3.15 CPython 3.15 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp315-cp315-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp315-cp315-manylinux_2_34_x86_64.whl CPython 3.15 CPython 3.15 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp315-cp315-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp315-cp315-manylinux_2_34_aarch64.whl CPython 3.15 CPython 3.15 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp315-cp315-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp314-cp314-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp314-cp314-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp314-cp314-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp314-cp314-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp314-cp314-manylinux_2_34_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp314-cp314-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp314-cp314-manylinux_2_34_aarch64.whl CPython 3.14 CPython 3.14 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp314-cp314-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp313-cp313-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp313-cp313-musllinux_1_2_aarch64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp313-cp313-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp313-cp313-manylinux_2_34_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp313-cp313-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp313-cp313-manylinux_2_34_aarch64.whl CPython 3.13 CPython 3.13 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp313-cp313-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp312-cp312-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp312-cp312-musllinux_1_2_aarch64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp312-cp312-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp312-cp312-manylinux_2_34_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp312-cp312-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp312-cp312-manylinux_2_34_aarch64.whl CPython 3.12 CPython 3.12 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp312-cp312-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp311-cp311-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp311-cp311-musllinux_1_2_aarch64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp311-cp311-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp311-cp311-manylinux_2_34_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp311-cp311-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp311-cp311-manylinux_2_34_aarch64.whl CPython 3.11 CPython 3.11 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp311-cp311-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp310-cp310-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp310-cp310-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp310-cp310-manylinux_2_34_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp310-cp310-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp310-cp310-manylinux_2_34_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp310-cp310-manylinux_2_34_aarch64.whl
httpperf-1.0rc3-cp39-cp39-musllinux_1_2_x86_64.whl CPython 3.9 CPython 3.9 Linux musl 1.2+ x86-64 Details for httpperf-1.0rc3-cp39-cp39-musllinux_1_2_x86_64.whl
httpperf-1.0rc3-cp39-cp39-musllinux_1_2_aarch64.whl CPython 3.9 CPython 3.9 Linux musl 1.2+ ARM64 Details for httpperf-1.0rc3-cp39-cp39-musllinux_1_2_aarch64.whl
httpperf-1.0rc3-cp39-cp39-manylinux_2_34_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.34+ x86-64 Details for httpperf-1.0rc3-cp39-cp39-manylinux_2_34_x86_64.whl
httpperf-1.0rc3-cp39-cp39-manylinux_2_34_aarch64.whl CPython 3.9 CPython 3.9 Linux glibc 2.34+ ARM64 Details for httpperf-1.0rc3-cp39-cp39-manylinux_2_34_aarch64.whl

Total release size: 127.3 MB

Release files / httpperf-1.0rc3.tar.gz

Download URL httpperf-1.0rc3.tar.gz
Size 69.3 kB
Tags Source
SHA-256 checksum
How to use checksums
34964c9192fb6ebfd4eea0a4ee1d3aafe52bc360ad9afa9149fe1a1677146a11
BLAKE2b-256 checksum
How to use checksums
80cf43a823f947daac041a566f40c989fadf483333045cdb853996d3d6abada3
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp315-cp315-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp315-cp315-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.15 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
dc986ada7585f1fa4db77ad7b63ec922fb4fce9ac58356f1df36fbb6c57bcfcf
BLAKE2b-256 checksum
How to use checksums
aeece4d46add5a90cbdaf9d1c9c27202035768aa3572e72e921d4182c8999085
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp315-cp315-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp315-cp315-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.15 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
4e51a7530cdd04e062ecaa46a05fd7b2c797527aa009f7e95c2d2799baf6d70e
BLAKE2b-256 checksum
How to use checksums
d0bbcfc375866022276ef4a96b8bc8dfab42db7f2e3bd042ea3d2d1afca14634
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp315-cp315-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp315-cp315-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.15 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
3389cddc2fbe07b22c87b2deab6cfd41cf5f86ca04292d0535c803b201c5337c
BLAKE2b-256 checksum
How to use checksums
a384597e5c2ab5fd7f01265d776bd740265aa2416da438c71298fd7e2460ec64
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp315-cp315-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp315-cp315-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.15 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
be54c941a9448bf7874aa631cada7acc57478ada2a5e3346e22fa79ae6786913
BLAKE2b-256 checksum
How to use checksums
5b0736509c2ed1bd2fa805c899d23cd2f3220b42c2ab7f9f9b41804806b4a866
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp314-cp314-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.14 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
d5125d9bab6d58c87f60c403c19512d6fb56f576c89f5760880eab74d3ae6ed1
BLAKE2b-256 checksum
How to use checksums
d5c8dc264dc211bc247dd0c72b98f9d7641b24299025e5aa41e667a2b30c1248
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp314-cp314-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.14 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
ad0a2e1250e04b0a23bdfb561a3fef2aa1cdb409eda11906227783ed8b080faa
BLAKE2b-256 checksum
How to use checksums
dbea7e6e8d7c9a3f1b0348749ca58d4649ed100d9db28088824e1ada418d8903
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp314-cp314-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
ca9877a36aa9f8d2c141894c591e699bb3b330494ccd16c93c499ca95e79edd1
BLAKE2b-256 checksum
How to use checksums
80e6377f60f8c98d34d7bea5c29743150fdd8fe21c38f6e3811fe1c9c6ab5868
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp314-cp314-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.14 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
b1b08f9807cb2520572e6e8424be1b02a26ed04a5503e262e0c3e4f690314bad
BLAKE2b-256 checksum
How to use checksums
d58658475d102b8cd7f1251de10463497b320d934fca64e4cf62740374710330
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp313-cp313-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
6e6569e04453dcf9b1e6efd0b3512430bcec575601193a801697147795f41e52
BLAKE2b-256 checksum
How to use checksums
7f8a22d4213944013e8cfe93760e854cbdce472a2ce8ca5f63c723835030d964
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp313-cp313-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.13 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
0cb92de952e437263619b754b65d4aff7eb72cb9a82033ce27075d388577db2c
BLAKE2b-256 checksum
How to use checksums
05d0dc050d740e166dd8c51f988dd2676f7d992b6bfcb15c7007f37273b6ec31
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp313-cp313-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
904f018fbef37cdfc0278953b14f2813a8b01e070cf3454525920ab953b65129
BLAKE2b-256 checksum
How to use checksums
601ec9ced464488d9d865ae450f4aa2a46f8ea8a2b507664cecf97360acb1819
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp313-cp313-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.13 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
a8087f4821fd584ae30bbb2308b61e26b343c5dd07b283ecb23a9d0c9e408ea4
BLAKE2b-256 checksum
How to use checksums
95eb2f22612411f131060ee3f2f9fde6b68dbcacdb6ec91021f90abf2841fecd
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp312-cp312-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
cb49173e6d362f803479ebc8a9ee938e1892a3ada6df8d7ac39fb2023fbcb115
BLAKE2b-256 checksum
How to use checksums
7a3a528fe24a56bc88e4c87d36d177cf4c348b599c848c606d7986ab15dd9489
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp312-cp312-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.12 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
1bcb275156e06b056401620a9961540f5c70e7e7372613f88cea7e043bf90afb
BLAKE2b-256 checksum
How to use checksums
b48e7d6b8e437a63fced9b6dfc639d7df2ae3ef413a9a02f5555ddd01a0896d0
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp312-cp312-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
32c152a04cdd1021ac8248b9326ac52d966d52d57823d077c4a2fc00ffdcb251
BLAKE2b-256 checksum
How to use checksums
7dbadb5c8efcf9d3903c5fc46e0c9dcb57e0784c1e1744d56598888892c4aaa3
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp312-cp312-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.12 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
5f98a7b6b3db20b8ced367abec2491787659addbacd67aed6bbde508c213c7c1
BLAKE2b-256 checksum
How to use checksums
93bd01ce625d53bc175e763c1d144439093a2f478f5bf167c236bee3eeb76146
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp311-cp311-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
3d77aaa9b727c82f658aff1809a0f50235bf3a5d91a7f14253d6a46ecdec0573
BLAKE2b-256 checksum
How to use checksums
d4a9b530ec590d498b406fdbfddae171d7cd1859ed02ac546b92f8718a42a907
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp311-cp311-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
4ffa229c3245d6f16000ad2ab214d6cc88292cbc333bc13725753b03406dc427
BLAKE2b-256 checksum
How to use checksums
48e8d9b4dff390fa1f8f7cd0920a0c8081672205276ee46d0e6b05cc3fa8fefc
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp311-cp311-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
1d59e4afe58e26aa7943de4e3ca98d5503b4fdc7c1c4a62980fbe5914b092386
BLAKE2b-256 checksum
How to use checksums
0aebfe0dbfbd3d40df96d8438443680ade6c358532c40603adb610566851ad61
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp311-cp311-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.11 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
dedb4bdb6309757eba9156b92a55d339312af4ac0a5c43e7012a2e81202a2f44
BLAKE2b-256 checksum
How to use checksums
5cae82dabbb851736a941458d8707020aba71de23e621a669a3ae1f06a58ffb4
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp310-cp310-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
75d0052d22c1779f3845051e9e0deb100e84aadec3f6545e46c87e4160afa994
BLAKE2b-256 checksum
How to use checksums
1e000308d8a767af0bfa5db937d56ee8e5258b9095daf2f048a246ebd646cfe3
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp310-cp310-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
35e56014ea3ac189d7def5b63b2bd3ed0e003145f6e1160b659499068a32530d
BLAKE2b-256 checksum
How to use checksums
ae8c97771309a4895a167c67569ffa90e658a30cb82633e175a161e445e0c5d8
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp310-cp310-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.10 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
f92ac86e35f8d908260edffc3ceee37075454e1a770e22abcc13ba0c94116f45
BLAKE2b-256 checksum
How to use checksums
e5fb259cedd10a38821357bf638be8039777eb412352490a27f3acb9ae10f3c7
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp310-cp310-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.10 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
8dca3cacbaca5bcc2418f14269e3fb8527ac4d28956eaf549630cfa0342fa7e0
BLAKE2b-256 checksum
How to use checksums
879e23b87885df02806f5147388c3736354351ec1c0e2c981e32e04ae50ba3bc
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp39-cp39-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc3-cp39-cp39-musllinux_1_2_x86_64.whl
Size 4.3 MB
Tags CPython 3.9 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
02566e5fd04f01fbb618d77e3c79bef7441ab725f4b7d07b9fbf6a484f616057
BLAKE2b-256 checksum
How to use checksums
c02912d47c0e11ebc2f1991394b66f9fbbc6d553b7ad97ae369986cb63128ac1
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp39-cp39-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc3-cp39-cp39-musllinux_1_2_aarch64.whl
Size 4.6 MB
Tags CPython 3.9 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
3b274848cb2bb81d93389e61b8c97b54e703bbd0ddc84642a6add170125ca87b
BLAKE2b-256 checksum
How to use checksums
8b5d556ad39e6da24e57d88bf599150b7a176e537bb0c38fdd6639238a8828bc
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp39-cp39-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc3-cp39-cp39-manylinux_2_34_x86_64.whl
Size 4.7 MB
Tags CPython 3.9 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
ebd6b05db75ce0f4436ad8c6f31bdb765ec71c715007977f52e4e265564cc292
BLAKE2b-256 checksum
How to use checksums
e153f358befe7747dd61ca6ee9f259336d7964af0dc6d628ce8a3b4a57dbf652
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 Nov 13, 2026.

Transparency log

Release files / httpperf-1.0rc3-cp39-cp39-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc3-cp39-cp39-manylinux_2_34_aarch64.whl
Size 4.5 MB
Tags CPython 3.9 Linux glibc 2.34+ ARM64
SHA-256 checksum
How to use checksums
d8cd06a328c27af2bfa7ddc8bf69211a873ed59dfa9aed4c1fde3cb2986b3653
BLAKE2b-256 checksum
How to use checksums
be911d372c4b135624a921170aa668ed2312be4d64a87fa40a26b81f0b424e4f
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 Nov 13, 2026.

Transparency log

Security for httpperf 1.0rc3

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 29 files in this release have been uploaded with provenance metadata.

Select from 29 files

Attestation for httpperf-1.0rc3.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 13, 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.

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