fix doctests to support numpy 1.24

[tornaria]

Taken from #34816.

This is necessary when system numpy is 1.24, and a prerequiste to update numpy in sagemath.

It's probably safer at this time to merge this and leave the update for next release.

Testing: void-linux/void-packages#42048

Depends on #35015

[mkoeppe]

LGTM

[vbraun]

merge conflict

[codecov-commenter]

Codecov Report

Base: 88.59% // Head: 88.58% // Decreases project coverage by -0.02% ⚠️

Coverage data is based on head (bf2a91c) compared to base (952a6c9).
Patch coverage: 97.05% of modified lines in pull request are covered.

❗ Current head bf2a91c differs from pull request most recent head 0195760. Consider uploading reports for the commit 0195760 to get more accurate results

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #34994      +/-   ##
===========================================
- Coverage    88.59%   88.58%   -0.02%     
===========================================
  Files         2140     2140              
  Lines       396961   396958       -3     
===========================================
- Hits        351695   351651      -44     
- Misses       45266    45307      +41     

Impacted Files	Coverage Δ
src/sage/algebras/free_algebra_element.py	82.50% <ø> (ø)
src/sage/algebras/fusion_rings/fusion_ring.py	93.93% <ø> (ø)
src/sage/algebras/lie_algebras/free_lie_algebra.py	95.43% <ø> (ø)
src/sage/algebras/lie_algebras/lie_algebra.py	91.10% <ø> (ø)
src/sage/algebras/lie_algebras/morphism.py	90.07% <ø> (ø)
src/sage/algebras/quatalg/quaternion_algebra.py	92.68% <ø> (ø)
src/sage/categories/category_with_axiom.py	98.71% <ø> (ø)
...age/categories/finite_complex_reflection_groups.py	79.12% <ø> (ø)
src/sage/categories/homset.py	92.66% <ø> (ø)
src/sage/categories/magmas.py	97.63% <ø> (ø)
... and 170 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[tornaria]

I don't know what is the merge conflict. Just in case, I rebased the two (quite small) commits on top of the current develop branch.

In fact the PR was saying I wanted to merge a lot of commits making changes to a lot of files, but I only want to merge 2 commits changing 4 files in minimal ways.

[mkoeppe]

I don't know what is the merge conflict.

The merge conflict was against Volker's branch. I had fixed the conflict already by merging #35015.

[tornaria]

I see. Two comments:
a. since merging is blocked, we don't see in a PR whether merging would be ok or not. When merging is not blocked, github will say whether the PR merges cleanly or not (see, e.g. void-linux/void-packages#42344, the message there is "This branch has no conflicts with the base branch when rebasing").
b. still, the merge conflict was against a different branch; the merge conflict detection would only work if the branch the PR is created against were the same as the branch where PR's are merged into.

The problem here is that once a very intrusive PR like #35015 is merged, we are all in the dark until that actually shows up in the develop branch.

[tornaria]

Rebased to 10.0.beta1, now it should be ok.

[github-actions]

Documentation preview for this PR is ready! 🎉
Built with commit: 0195760

outdated