urllib3 Use the `typing.` namespace consistently throughout

The Fix

pip install urllib3==1.26.13

Based on closed urllib3/urllib3 issue #2789 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -1,3 +1,5 @@
@@ -1,3 +1,5 @@
+from __future__ import annotations
+
 import os

fix.md

Option A — Upgrade to fixed release\npip install urllib3==1.26.13\nWhen NOT to use: Do not apply this fix if the project requires backward compatibility with older Python versions.\n\n

Why This Fix Works in Production

Trigger: Let's change all occurrences of `from typing import X` into `import typing` and then use `typing.X`.
Mechanism: Inconsistent use of typing namespace led to module namespace pollution
Why the fix works: Replaces `import typing.X; X` with `import typing; typing.X` throughout the project. (first fixed release: 1.26.13).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Inconsistent use of typing namespace led to module namespace pollution
Production symptom (often without a traceback): Let's change all occurrences of `from typing import X` into `import typing` and then use `typing.X`.

Proof / Evidence

GitHub issue: #2789
Fix PR: https://github.com/urllib3/urllib3/pull/2813
First fixed release: 1.26.13
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.85
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.86

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“This is probably only practical if we merge #2779”

@pquentin · 2022-11-10 · source

Failure Signature (Search String)

Let's change all occurrences of `from typing import X` into `import typing` and then use `typing.X`.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Let's change all occurrences of `from typing import X` into `import typing` and then use `typing.X`.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Let's change all occurrences of `from typing import X` into `import typing` and then use `typing.X`.

What Broke

Potential confusion and errors in type hinting across the codebase.

Why It Broke

Inconsistent use of typing namespace led to module namespace pollution

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install urllib3==1.26.13

When NOT to use: Do not apply this fix if the project requires backward compatibility with older Python versions.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Option D — Guard side-effects with OnceOnly Guardrail for side-effects

Mitigate duplicate external side-effects under retries/timeouts/agent loops by gating the operation before calling external systems.

Place OnceOnly between your code/agent and real side-effects (Stripe, emails, CRM, APIs).
Use a stable key per side-effect (e.g., customer_id + action + idempotency_key).
Fail-safe: configure fail-open vs fail-closed based on blast radius and spend risk.

Show example snippet (optional)

onceonly.py

from onceonly import OnceOnly
import os

once = OnceOnly(api_key=os.environ["ONCEONLY_API_KEY"], fail_open=True)

# Stable idempotency key per real side-effect.
# Use a request id / job id / webhook delivery id / Stripe event id, etc.
event_id = "evt_..."  # replace
key = f"stripe:webhook:{event_id}"

res = once.check_lock(key=key, ttl=3600)
if res.duplicate:
    return {"status": "already_processed"}

# Safe to execute the side-effect exactly once.
handle_event(event_id)

See OnceOnly SDK

When NOT to use: Do not use this to hide logic bugs or data corruption. Use it to block duplicate external side-effects and enforce tool permissions/spend caps.

Fix reference: https://github.com/urllib3/urllib3/pull/2813

First fixed release: 1.26.13

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

Do not apply this fix if the project requires backward compatibility with older Python versions.
Do not use this to hide logic bugs or data corruption. Use it to block duplicate external side-effects and enforce tool permissions/spend caps.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Add a CI check that diffs key outputs after upgrades (OpenAPI schema snapshots, JSON payload shapes, CLI output).
Upgrade behind a canary and run integration tests against the canary before 100% rollout.

Version Compatibility Table

Version	Status
1.26.13	Fixed

Related Issues

No related fixes found.

Cluster: urllib3:configuration-error urllib3 hub urllib3 best practices All hubs All clusters

Related clusters: Data consistency SSL handshake Other

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.

urllib3 Use the `typing.` namespace consistently throughout the project (Fix)