Repository navigation
TST: devdeps failing with numpy-dev failures from mpl #15283
Description
Thanks to @neutrinoceros for the notice. We will just have to wait it out. Original post on Slack as follows.
In case I can save anyone else from chasing their tail today: there are a couple failures in future-compatibility tests today that are due to matplotlib using newly deprecated API in future numpy. The problem was already fixed upstream 2 weeks ago, it's just that pip sees matplotlib 3.8.0rc1 (which doesn't have the patch) as more "recent" than the nightly wheel, so I don't think there's anything we can do but wait for a new release, or nightlies with a version number starting with "3.9"
For reference:
Activity
neutrinoceros commentedon Sep 6, 2023
if it takes to long to resolve itself, we could upstream the discussion to matplotlib and suggest they name their nightly wheels in a way that makes it clear to
pipthat they are actually more up to date than the current release candidate.pllim commentedon Sep 6, 2023
Given that we have pinned
numpy<2in both v5.0.x and v5.3.x, and we not planning to release v6 for a few months yet, there is no big rush. I would give them a couple of weeks. Thanks! 😸neutrinoceros commentedon Sep 6, 2023
Took me long enough to even think about it but I suppose we might be able to avoid this with
--only-binary matplotlib. I haven't tried it yet and won't be able to for an hour or two so anyone is welcome to have a go at it !pllim commentedon Sep 6, 2023
We used to have
--only-binaryflag and then for some reason we removed it. I don't quite remember why. Feel free to try if you want. I won't have time for this today. Thanks!