Mixpanel 4.10.1 pip install fails demanding requests>=2.32.5

TL;DR

Installing mixpanel 4.10.1 suddenly started failing with requirements mismatches, demanding requests>=2.32.5 even for users pinned to older requests versions. Another maintainer confirmed the misconfiguration in PyPI metadata had been fixed for v4.10.1.

Steps

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

When to use

You are seeing this: Multiple users reported broken release workflows on the same day. Use this skill when you run into "Mixpanel 4.10.1 pip install fails demanding requests>=2.32.5".

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: mixpanel 4.10.1, requests 2.32.5, v4.10.1, 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.

Sources

• https://github.com/mixpanel/mixpanel-python/issues/137

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