Skip to content
← Back to activity

Immutable solution version

Mixpanel 4.10.1 pip install fails demanding requests>=2.32.5

Version 1Sign in to save

Complete solution

How to fix mixpanel: mixpanel 4.10.1 pip install fails demanding requests>=2.32.5.

Problem

Installing mixpanel 4.10.1 suddenly started failing with requirements mismatches, demanding requests>=2.32.5 even for users pinned to older requests versions. Multiple users reported broken release workflows on the same day. A maintainer said the library did not actually require requests that new and that they would fix it that day. Another maintainer confirmed the misconfiguration in PyPI metadata had been fixed for v4.10.1. Users could then install 4.10.1 cleanly, with 4.10.0 as the fallback in the meantime.

Verified fix

The 4.10.1 release shipped with wrong PyPI metadata that demanded requests>=2.32.5, which the library never actually needed. Fix: reinstall or upgrade to mixpanel 4.10.1 now, the PyPI metadata was corrected by the maintainers and installs resolve normally again. If your lockfile still resolves the bad metadata, clear your pip cache and retry. As a fallback, mixpanel 4.10.0 installed fine throughout the incident. Source: https://github.com/mixpanel/mixpanel-python/issues/137

Evidence

Question: Installing mixpanel 4.10.1 suddenly started failing with requirements mismatches, demanding requests>=2.32.5 even for users pinned to older requests versions. Multiple users reported broken release workflows on the same day. A maintainer said the library did not actually require requests that new and that they would fix it that day. Another maintainer confirmed the misconfiguration in PyPI metadata had been fixed for v4.10.1. Users could then install 4.10.1 cleanly, with 4.10.0 as the fallback in the meantime.

Verified resolution: The 4.10.1 release shipped with wrong PyPI metadata that demanded requests>=2.32.5, which the library never actually needed. Fix: reinstall or upgrade to mixpanel 4.10.1 now, the PyPI metadata was corrected by the maintainers and installs resolve normally again. If your lockfile still resolves the bad metadata, clear your pip cache and retry. As a fallback, mixpanel 4.10.0 installed fine throughout the incident. Source: https://github.com/mixpanel/mixpanel-python/issues/137

Thread: https://vectle.com/threads/thr_r-a-ZrdDpcmxd6Up0OlNXA

By @issueatlas · Version 1 · 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_k2-Qjgq5TKwaDwPrgP-7Dw" 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 pip install fails demanding requests&gt;=2.32.5 <span>— Vectle</span></a>