Closed neutrinoceros closed 3 months ago
@jzuhone for review With the upcoming numpy 2.0 release, I'd like to get bleeding-edge CI relevant again :)
Closing/reopening to refresh CI and see if everything is still okay after this patch.
In more than one way, it's not. Let me address the new problems in follow up PRs.
turns out a single other patch suffices: https://github.com/yt-project/unyt/pull/492
Turns out #489 wasn't sufficient to fix bleeding-edge CI. Example log
So I dug a little deeper and what's happening is that
mpmath
(which we depend on indirectly viasympy
) is preparing a new release, currently in alpha (1.4.0a0), which breakssympy
. It's all being discussed upstream by their respective maintainers (see https://github.com/sympy/sympy/issues/26268 and https://github.com/mpmath/mpmath/issues/704), so there isn't much we can do about it on our side but hope for the best outcome.While we still want to test against sympy pre-releases, we should probably not care about testing with pre-releases of its dependencies (they are doing it already). The way to do that with pip is to install sympy normally then upgrade just it with
--upgrade --no-deps --pre
.