Repository navigation
TST: Use legacy numpy 1.25 print - #15096
Conversation
|
Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.
|
|
👋 Thank you for your draft pull request! Do you know that you can use |
|
pre-commit.ci autofix |
|
Hmm didn't fix everything; 10 of the remaining 13 failures are related. |
|
I can push what I had but those remaining test failures should be fixed upstream -- clearly, we missed some legacy if statement here, so pinging @seberg. |
|
I retriggered a build with the fix so you can iterate (in 30 minutes). I hope you are not using |
|
Well, since you brought up Both numpy and scipy are from dev wheels hosted by Scientific Python. Update: Looks like scipy removed it in scipy/scipy#18973 so I guess they have to push a new dev wheel out? |
|
Yeah, scipy is working on that, sorry. (not sure if you use it, if you do chime in your opinion if you think it should stay; personally, I actually don't think |
I do not use it personally, no. But I will wait to see what the CI here says until scipy dev wheel gets updated. Thanks for the heads up! |
|
Only one related failure left! |
This comment was marked as resolved.
This comment was marked as resolved.
|
@WilliamJamieson is aware of the modeling stuff but not sure when he has time to fix those... |
This comment was marked as resolved.
This comment was marked as resolved.
|
Agreed that we should wait out the |
12e5d13 to
ea2f8e4
Compare
ea2f8e4 to
d3a463d
Compare
| else: | ||
| # See whether it covers our dtype. | ||
| from numpy.core.arrayprint import _get_format_function | ||
| from numpy.core.arrayprint import _get_format_function, _make_options_dict |
There was a problem hiding this comment.
@mhvk , should we not use hidden functions from deep within numpy? I am afraid further refactoring upstream will come back to bite us here.
There was a problem hiding this comment.
In principle, yes, and clearly here my initial implementation was even wrong! (since without _make_options_dict, the legacy option does not get properly translated into an integer). But the alternative is duplication of the whole arrayprint module...
Anyway, I hope this will become moot: in the initial scalar work, a public version of _get_format_function was included, and I think this is still likely to happen. Once that is there, we can just switch to using it.
so the new numpy 2.0 print will not break CI until we are ready to patch it properly.
from nddata test
a957751 to
5433c6d
Compare
because we moved it for pydata-sphinx-theme
tests for modeling when TRFLSQFitter is used
There was a problem hiding this comment.
@WilliamJamieson , I went ahead and kinda ignore the new modeling warnings from scipy dev. Will open a follow-up issue for you later.
There was a problem hiding this comment.
Actually I will just update #15087 when this is merged.
|
pre-commit.ci autofix |
|
argh devdeps finally green... |
|
Wut? Why would cosmology doctest fail only on s390x? @nstarman , do you know what is going on here? |
|
I noticed something similar to this in a recent PR (#15102) if you want to cherry-pick the fix. |
mhvk
left a comment
There was a problem hiding this comment.
Thanks! I think these changes all look fine, and it may be best to just merge this, and work on other issues separately.
p.s. It would seem there is a case for keeping the different commits separate (for possible reversion later on).
…096-on-v5.3.x Backport PR #15096 on branch v5.3.x (TST: Use legacy numpy 1.25 print)
Description
This pull request is to use legacy numpy 1.25 print so the new numpy 2.0 print will not break CI until we are ready to patch it properly over at #15065.
Temporary workaround for #15095
This patch is as suggested by
sebergover at astropy/pyvo#464 (comment) and similar tobsipoczpatch at astropy/pyvo#465 .