requests-wasi-http
A requests transport adapter for
WASI HTTP (wasi:http@0.2), so
requests works inside WebAssembly components built with
componentize-py.
import requests
import wit_world # the componentize-py bindings for your WIT world
from wasi_http_adapter import WasiHttpAdapter
session = requests.Session()
adapter = WasiHttpAdapter(wit_world) # or WasiHttpAdapter("wit_world")
session.mount("https://", adapter)
session.mount("http://", adapter)
response = session.get("https://postman-echo.com/get", timeout=5)
print(response.status_code, response.json())
Or use the convenience factory:
session = wasi_http_adapter.wasi_session(wit_world).
The adapter never guesses where the bindings live: pass the componentize-py
bindings package for your WIT world (a world that imports
wasi:http/outgoing-handler) explicitly, either as the imported package
object or as its name.
Cookies, redirects, timeouts, and streaming downloads (stream=True) work
through a regular Session. TLS verification, client certificates, and
proxies are owned by the WASI host and therefore ignored; Accept-Encoding
is forced to identity since there is no transparent decompression.
Development
uv run pytest # tests
uv run ruff format . # format
uv run ruff check . # lint
uv run ty check # types
Metadata
Release files for requests-wasi-http 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| requests_wasi_http-0.1.0.tar.gz | 28.0 kB | Without provenance | Details for requests_wasi_http-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| requests_wasi_http-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for requests_wasi_http-0.1.0-py3-none-any.whl |
Total release size: 36.5 kB
Release files / requests_wasi_http-0.1.0.tar.gz
| Download URL | requests_wasi_http-0.1.0.tar.gz |
|---|---|
| Size | 28.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52f94b9231d40eefcd8c26266a22e771c20d340608d7578d12e400b97161e79a
|
|
BLAKE2b-256 checksum How to use checksums |
1d157493616ff1d2ce5f5cf407b7e956ba8eb015050b791990dd7c4d20c57d5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.11 {"installer":{"name":"uv","version":"0.12.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / requests_wasi_http-0.1.0-py3-none-any.whl
| Download URL | requests_wasi_http-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b007b83d52f60a4edf7aaa3d49cf7558b2d0dd403b516c2a4e7cc6b360a76154
|
|
BLAKE2b-256 checksum How to use checksums |
0eeed54a5adc0047e3fa52a51dcc5a11396d69e703125b3f63ef0e70b9226fe5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.11 {"installer":{"name":"uv","version":"0.12.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for requests-wasi-http 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.