Fix one more doctest failure with Python 3.14#41394
Merged
vbraun merged 1 commit intosagemath:developfrom Jan 6, 2026
Merged
Conversation
Seems to have been missed in sagemath#41086
|
Documentation preview for this PR (built with commit 58aa8c4; changes) is ready! 🎉 |
Contributor
|
Are you sure you picked the right commit? |
Member
Author
yes, why? |
Contributor
|
Because your commit here only adds some text, it is different from the commit 5de7542 that you referenced in the other pr. |
Member
Author
Contributor
|
Yes, It deal with a different doctest issue. |
Contributor
|
I see, sorry about the noise. Would you mind pointing out which failure this is fixing? |
Contributor
The doctest failure only happens in python 3.14 |
Contributor
|
I understand that, this is also what I am using on Void. |
Member
Author
|
cxzhong
approved these changes
Jan 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seems to have been missed in #41086