AW-1: request() wraps a total ClientTimeout's bare asyncio.TimeoutError before request_with_retries sees it, so the dedicated 'timeout' branch was dead and its comment lied. wrap it as aiohttp.ServerTimeoutError (which IS both a ClientError AND a TimeoutError) so direct request() callers still get a typed failure (M1 preserved) while request_with_retries catches the timeout case first and labels it 'timeout'. verified by execution: request() raises ServerTimeoutError (typed, M1 intact); request_with_retries returns reason='timeout'; control confirms a real client error still labels 'client error'. sibling-grep: aioweb_tls/aiowebhooks catch ClientError/TimeoutError, both of which ServerTimeoutError satisfies — no consumer break. Signed-off-by: disqualifier <dev@disqualifier.me>
21 lines
536 B
TOML
21 lines
536 B
TOML
[build-system]
|
|
requires = ["hatchling"]
|
|
build-backend = "hatchling.build"
|
|
|
|
[project]
|
|
name = "aioweb"
|
|
version = "0.1.5"
|
|
description = "Async HTTP session wrapper over aiohttp — proxies, header overwrites, retries, previews. Config-free, installable."
|
|
requires-python = ">=3.10"
|
|
dependencies = [
|
|
"aiohttp>=3.9",
|
|
"yarl>=1.9",
|
|
"commons @ git+ssh://git@git.rethinkstudios.io/rethink-public/commons.git@v0.2.1",
|
|
]
|
|
|
|
[tool.hatch.metadata]
|
|
allow-direct-references = true
|
|
|
|
[tool.hatch.build.targets.wheel]
|
|
packages = ["src/aioweb"]
|