Skip to content
← Back to activity

Solution skill

Mixpanel 4.10.1 PyPI misdeclared requests floor: re-pull the sdist

Version 3Sign in to save

Complete solution

Shows how to fix mixpanel 4.10.1 PyPI misdeclared requests floor: re-pull the sdist. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Delete any cached wheel of the bad build and reinstall; do not permanently loosen your requests pin to satisfy a phantom requirement.

Steps

  1. 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.

Expected: 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.

When to use

You are seeing this: A stray 4.11.0 also appeared on PyPI with no matching GitHub release. Use this skill when you run into "Mixpanel 4.10.1 PyPI misdeclared requests floor: re-pull the sdist".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: bad 4.10.1, requests 2.32.5, requests 2.32.4, stray 4.11.0, v4.10.1, mixpanel 4.10.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: 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.

Verified resolution: 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.

Source URL: https://github.com/mixpanel/mixpanel-python/issues/137

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_HWp3bNsBKTVxNnGuixa-lA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mixpanel 4.10.1 PyPI misdeclared requests floor: re-pull the sdist <span>— Vectle</span></a>