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 CAs, from the first of: SSL_CERT_FILE and SSL_CERT_DIR, if set and present; libcurl's own default bundle, if present; Python's default bundle (ssl.get_default_verify_paths()); the usual system locations. 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.0rc4

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.0rc4
File Size Uploaded Provenance Actions
httpperf-1.0rc4.tar.gz 71.8 kB With provenance Details for httpperf-1.0rc4.tar.gz

Built distributions (wheels)

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

Total release size: 127.4 MB

Release files / httpperf-1.0rc4.tar.gz

Download URL httpperf-1.0rc4.tar.gz
Size 71.8 kB
Tags Source
SHA-256 checksum
How to use checksums
fbfa7cb13b67b4ae972a4cc39ca19c8ee2ddc7469fa439f42948a37311650707
BLAKE2b-256 checksum
How to use checksums
f35dd05c5db627cdf74c5860131b516dc154221088ccdad521135c157f9e8d34
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.0rc4-cp315-cp315-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
80644d409f1c17cf632d5b9642d3265b7e0e515302d90303017d40442bb88762
BLAKE2b-256 checksum
How to use checksums
a001a361ff954ea0dc22984bfd70ec98c309d430c73ab8338667afc23d468205
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.0rc4-cp315-cp315-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
f414199a717e3edd7e079a1ded93cae55fb092b6d8530c4eeeb675c6172be7b5
BLAKE2b-256 checksum
How to use checksums
f439ff04e36b1895882a17739b1f48a3fe948e7bd1799b45311a32e7a780cf64
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.0rc4-cp315-cp315-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-cp315-cp315-manylinux_2_34_x86_64.whl
Size 4.8 MB
Tags CPython 3.15 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
db90e7f1d8692c242c7dce1eb26dae2f8ce9c75451c17466b55a1928d441a5bd
BLAKE2b-256 checksum
How to use checksums
d8643429db04238c197a675137814ec7611b5b9ab429dfbf0eca9644edf3cdc3
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.0rc4-cp315-cp315-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
9e438f1024401a65ffffe53f3f0ef899f374e646d976b30184b4d74e87984311
BLAKE2b-256 checksum
How to use checksums
976ea2d816d375ee5267703b0c6cd999e5ad483816f023d0905c08e783bd3f74
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.0rc4-cp314-cp314-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
cfcf1ded0dc8754096817d74ddf8154376b04000da0b491b059bdbf1e71e81a1
BLAKE2b-256 checksum
How to use checksums
63c815086abcf6dfd9d62e59061a4d41a08e6cf5440e0ea9d9ff4dcc76d93737
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.0rc4-cp314-cp314-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
9a4724d542d78c424f80f8f2470a85c1dd22d4138e205c2635b0903b062aa717
BLAKE2b-256 checksum
How to use checksums
9ea43192f417bdbd4598ab0b90355aac10b48f81bc12539cea120d1b9ca0002f
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.0rc4-cp314-cp314-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-cp314-cp314-manylinux_2_34_x86_64.whl
Size 4.8 MB
Tags CPython 3.14 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
74015adfebaa8a572396b1b064aaf86db8e3f7bd636ddc7584e8ef37319bf39b
BLAKE2b-256 checksum
How to use checksums
d3a9a5d36f56f9c6539ff7b6d51eb894be013e083de6208791e9d19ca8f8159d
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.0rc4-cp314-cp314-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
fb914c6dc71b7ca4ab3b76cd0c519fb5554dd4cfe0b3942b2680a2535659a0a2
BLAKE2b-256 checksum
How to use checksums
2ac304f5493df2af3251c860888d490ac2a6ac6b6ee829de66e8bc81ce8a0a05
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.0rc4-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
da8fc6a1ea6e3b502bbc73fa4b7f5f8034344086d7c929244f0bea9691834732
BLAKE2b-256 checksum
How to use checksums
6babd0f97dad53ea47e8e96ddd742042acbdeebd26cd26544fbd9c1ed123e2ba
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.0rc4-cp313-cp313-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
1344242d461a36e96eb7732bf9584608e699dc94852fdc6f3c4bd404274bcd87
BLAKE2b-256 checksum
How to use checksums
9e6b88b893c853d6968d8686b7e478148070f388d38d9b93d21007a84381b654
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.0rc4-cp313-cp313-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-cp313-cp313-manylinux_2_34_x86_64.whl
Size 4.8 MB
Tags CPython 3.13 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
01a3c299d337a11b33f34e500824fa352fe737e05715f3dc4761b19f9c9e3606
BLAKE2b-256 checksum
How to use checksums
d7070d0a5948b35806c88b9894e54132b26f5b53bc178e83d812cef959f2a9d7
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.0rc4-cp313-cp313-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
11e3f10abe4a42e63179015d67c4597650e8e0b01242414b3c4b9594d1ff810b
BLAKE2b-256 checksum
How to use checksums
28162b7ef0cedf2b3a55044a4e774d13bd409a8e6fe935e1959ac4b9ee3f1148
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.0rc4-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
81b341fbb6b98af559a8265315381fd3a64818a88ec95af1c7a77241a4bf00f0
BLAKE2b-256 checksum
How to use checksums
9d1bd1df948e803809a5736ea56d61ebb1c928405c0aae659085a7561d0504a0
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.0rc4-cp312-cp312-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
3b2b58e36a9175c1bd17925fb4a691b7889e5d4c9f8b014ddba3bcbab567e179
BLAKE2b-256 checksum
How to use checksums
7f91d129177cba2f709d8ed862bd31fa2f2e35c0d6d50ed05ef9d63c81f1c580
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.0rc4-cp312-cp312-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-cp312-cp312-manylinux_2_34_x86_64.whl
Size 4.8 MB
Tags CPython 3.12 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
175f9a90b2240f180149dc1dcafae5bf858761e12611eead51990502d0fc278c
BLAKE2b-256 checksum
How to use checksums
79db496c9926388f2f3a2e8c35691ead7ce2f50f14bed6d986e2a4757a352ee5
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.0rc4-cp312-cp312-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
67c3531ce8e8cad5256f95c4c70ad18dacba507fa91a96d39cb93a4c736274b3
BLAKE2b-256 checksum
How to use checksums
d48e7ca8867d012f82897f8d4436fc525f5d3bbfdda6a3d405b7aa18e9351e34
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.0rc4-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
d9ccce79031eda6f2de19baee66eccdcc1580d4576ca5271417ed31cb6a296c4
BLAKE2b-256 checksum
How to use checksums
4aaf221c2e3cae6cf31370369ab10367229af1cf4fb8d8a1a078605154db4776
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.0rc4-cp311-cp311-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
98c6acb2d5c9d86acec724fd5c1d1590bd7a5e16727a1970442ab78eb3b84b58
BLAKE2b-256 checksum
How to use checksums
409994ef1e7bad60fb77d0e1892f58080647713faa88e7e2db46d303ae377a51
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.0rc4-cp311-cp311-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-cp311-cp311-manylinux_2_34_x86_64.whl
Size 4.8 MB
Tags CPython 3.11 Linux glibc 2.34+ x86-64
SHA-256 checksum
How to use checksums
de5a82c495f8d861cc1a8c11eb04777602eae7bba44d01792356e976373cf437
BLAKE2b-256 checksum
How to use checksums
68287137f44f82c395b9832f318d3e9d7dc9f9bed0cced472bcd757ed52c436e
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.0rc4-cp311-cp311-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
cc3c7628d069a998752db5123fb6909b764f5ce5154ae5cf6a7c2cbd56b41241
BLAKE2b-256 checksum
How to use checksums
97f4ef89d245e407198c7e5cf991159144c7050f6510dab19cffcafeda49d4fe
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.0rc4-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
d9ecea0a09998cc0ca18f9eee422f5f33662380807635c6caa094f1d1a90181e
BLAKE2b-256 checksum
How to use checksums
b54bed116fef83249b1bbed8ac33b79d675f85e4c314cd9e930e7b9d7e9fd18e
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.0rc4-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
efc15d79f08d45bfaa61e7b25cde547e97023fd4b78661b1183515f4ef931a02
BLAKE2b-256 checksum
How to use checksums
9620b15835deb9f26b9c7285e218c974abb093647524de3a399c52f5aa7b3c8c
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.0rc4-cp310-cp310-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-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
6dbbbf899009edac7694722b26177ac9033d9faf119d6ba26513ba119bff0bc5
BLAKE2b-256 checksum
How to use checksums
74232bb05df328d2ae7eb3c0a48851c801e988f8a9af53ce7816b2b0b636b85e
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.0rc4-cp310-cp310-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
95b78e2a951f019c3799df7f73b2ed17fc55fab0dc15078e1c16e119c3147d77
BLAKE2b-256 checksum
How to use checksums
907414c3aab48adc91c88c87065d641c0a686fbf783d984807d11002eff85dc0
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.0rc4-cp39-cp39-musllinux_1_2_x86_64.whl

Download URL httpperf-1.0rc4-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
0cf04e6f3ff24e2ad1fd43f7e509e7ed3d5954bd1e4e3783bf2a45c1cc17b065
BLAKE2b-256 checksum
How to use checksums
8d2bd2516081eda8c91f5ff2c1a5291c654d99d0616dcd7a689ce410c26e84b1
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.0rc4-cp39-cp39-musllinux_1_2_aarch64.whl

Download URL httpperf-1.0rc4-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
97f6761d8035ffbfb89b1f0f310f0e3cec6d6969e45477faeaf57d6f9e4fcbf9
BLAKE2b-256 checksum
How to use checksums
f2eae2839335c1686d716017c0c6570c4ba3b747b13e25bb772c4a9304d389d3
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.0rc4-cp39-cp39-manylinux_2_34_x86_64.whl

Download URL httpperf-1.0rc4-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
66f6c7539832350d5998913b97f25e786125ea5a8c9f3d751bb87f9fa253a41c
BLAKE2b-256 checksum
How to use checksums
f21711a6fd214602a338043afd339afb3c6cfe1b71444293ac959d3637f7524d
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.0rc4-cp39-cp39-manylinux_2_34_aarch64.whl

Download URL httpperf-1.0rc4-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
111c9c8264030220b9f9e70b13e6ef70b1c61923b1f895bbe2e1122dc7eb2ac6
BLAKE2b-256 checksum
How to use checksums
4d6d83b942ed8276fdb4e7af89e745c77f9eacd7add23907157c822c424e6d42
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.0rc4

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.0rc4.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