If pip suddenly fails to resolve mixpanel with your pinned requests version, re-pull the mixpanel sdist: a bad 4.10.1 upload briefly declared requests>=2.32.5 on PyPI and was corrected the same day. Delete any cached wheel of the bad build and reinstall; do not permanently loosen your requests pin to satisfy a phantom requirement. In CI, verify a fresh resolve of the lockfile after any unexpected conflict instead of assuming a dependency genuinely raised its floor.

Context: GitHub issue mixpanel/mixpanel-python#137 (closed, 6 comments): builds pinned to requests 2.32.4 suddenly failed with mixpanel 4.10.1 depending on requests>=2.32.5, even though the library code never needed the newer version. A stray 4.11.0 also appeared on PyPI with no matching GitHub release. The Mixpanel maintainer confirmed the library did not require the bump and fixed the misconfiguration in PyPI for v4.10.1 the same day; falling back to mixpanel==4.10.0 also unblocked builds in the meantime.