Closed erykoff closed 3 months ago
Yeah, we plan to push out v6.1.1 when numpy 2.0 is released, I think. cc @mwcraig @astrofrog @saimn @neutrinoceros
I assume this is related to https://github.com/astropy/astropy/issues/16423 and that released versions of astropy are not yet numpy2 compatible.
Depends what kind of failure you're seeing. Astropy 6.1.0 was intended to be numpy2 compatible but indeed we missed a couple issues regarding string representation of scalars. All known issues have known solutions (3/5 already merged and backported). I think we should probably cut a 6.1.1 when we get them all in, and that waiting for numpy 2.0.0 final would only expose end users to these issues (6.1.0 removed the <2
pin).
However, I'd like to know more about the failures you're seeing. If you still get any with np.set_printoptions(legacy="1.25")
, that would need to be reported, otherwise, we're already on it ! :-)
@erykoff could you specify the list of tests you saw fail please ? We have addressed every known issue in main and are set for a truly compatible 6.1.1 release, I would feel more comfortable knowing we haven't left anything out.
Should have been fixed by #138
I cannot close this, so please close it. Thanks.
Solution to issue cannot be found in the documentation.
Issue
The PR #135 was merged, but I am finding a lot of test failures using this build/version. I assume this is related to https://github.com/astropy/astropy/issues/16423 and that released versions of astropy are not yet numpy2 compatible.
I should note that the PR bot added the comment
Installed packages
Environment info