Requests Conflicting requirements for urllib3 (Fix)

The Fix

pip install requests==2.32.0

Based on closed psf/requests issue #6544 · 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

@@ -7,7 +7,7 @@ requires-dist =
     charset_normalizer>=2,<4
     idna>=2.5,<4
-    urllib3>=1.21.1,<1.27
+    urllib3>=1.21.1,<3

fix.md

Option A — Upgrade to fixed release\npip install requests==2.32.0\nWhen NOT to use: Do not apply if the version requirements are already aligned.\n\n

Why This Fix Works in Production

Trigger: Inconsistent dependency resolution leading to potential installation issues.
Mechanism: Fixes the conflicting requirements for urllib3 in setup.cfg by aligning the version restrictions.
Why the fix works: Fixes the conflicting requirements for urllib3 in setup.cfg by aligning the version restrictions. (first fixed release: 2.32.0).

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

Production symptom (often without a traceback): Inconsistent dependency resolution leading to potential installation issues.

Proof / Evidence

GitHub issue: #6544
Fix PR: https://github.com/psf/requests/pull/6545
First fixed release: 2.32.0
Reproduced locally: No (not executed)
Last verified: 2026-02-08
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.79

Discussion

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

Jump to Sources Open on GitHub

“They should, good catch xypron. We'll work on getting those aligned.”

@nateprewitt · 2023-10-06 · source

Failure Signature (Search String)

Inconsistent dependency resolution leading to potential installation issues.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Inconsistent dependency resolution leading to potential installation issues.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Inconsistent dependency resolution leading to potential installation issues.

What Broke

Inconsistent dependency resolution leading to potential installation issues.

Fix Options (Details)

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

pip install requests==2.32.0

When NOT to use: Do not apply if the version requirements are already aligned.

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

Fix reference: https://github.com/psf/requests/pull/6545

First fixed release: 2.32.0

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

When NOT to Use This Fix

Do not apply if the version requirements are already aligned.

Did This Fix Work in Your Case?

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

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
2.32.0	Fixed

Related Issues

No related fixes found.

Cluster: requests:configuration-error Requests hub Requests 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.