Repository navigation
BUG: fix bugs in io.votable related to numpy 2's representation of scalars - #16442
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 |
87fb0e8 to
e624fdf
Compare
|
pyvo and/or astroquery might want to review this. I will ping them. |
mhvk
left a comment
There was a problem hiding this comment.
Yes, that looks like a better fix than I had!
One question, but nothing depends on it, so I'll approve now.
|
|
||
|
|
||
| @pytest.mark.xfail("legacy_float_repr") | ||
| @pytest.mark.usefixtures("without_legacy_printoptions") |
There was a problem hiding this comment.
Could we just do it for the whole test file?
There was a problem hiding this comment.
In principle yes but there doesn't seem to be a need for it: tests that fail without legacy print options are actually pretty rare in the code base so I don't expect to find more when we remove the global setting, which we should be able to do as soon as we merge #15065
…alars Co-authored-by: Marten van Kerkwijk <[email protected]>
e624fdf to
2bec9ce
Compare
|
The |
|
OK, let's get this in as well! |
…py 2's representation of scalars
…442-on-v6.1.x Backport PR #16442 on branch v6.1.x (BUG: fix bugs in io.votable related to numpy 2's representation of scalars)
Description
This pull request is to address part of #16423 (specifically,
io.votable).The first commit is common with #16426, #16427 and #16433 (allowing them to be merged in arbitrary order).The fix itself is in part taken from #15065