-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doctest failures due to hard-coded line numbers in (doctests of) sage/rings/*.pyx #9859
Comments
comment:1
Minh, please excuse and change the component in case it's the wrong one. (I'm not sure if "doctest" refers to the framework or doctest failures in general.) |
Based on Sage 4.5.3.rc0. Apply to Sage library. |
Changed work issues from Replace line numbers in doctests by ellipses. to none |
comment:2
Attachment: trac_9859-fix_hard-coded_doctest_line_numbers.patch.gz Ok, I'm a beginner. ;-) (I've uploaded a patch.) |
Author: Leif Leonhardy |
comment:3
Those hard-coded line numbers that leif fixed shouldn't have been there in the first place. The patch applied OK against Sage 4.5.3.rc0, all doctests (including long) passed, and the standard documentation built fine. And I'm OK with the changes in the patch. |
Reviewer: Minh Van Nguyen |
comment:4
Replying to @sagetrac-mvngu:
Yes. According to Mercurial, Michael Abshoff introduced that in Jan 2009(!)... :-) I wonder why I never ran into this before, since I frequently doctest with modified versions of Thanks for reviewing this. |
Merged: sage-4.6.alpha1 |
These failures occurred just because some line numbers in
$SAGE_LOCAL/bin/ncadoctest.py
changed (when I added some flush statements).Component: doctest coverage
Keywords: DeprecationWarning failure integer.pyx rational.pyx beginner
Author: Leif Leonhardy
Reviewer: Minh Van Nguyen
Merged: sage-4.6.alpha1
Issue created by migration from https://trac.sagemath.org/ticket/9859
The text was updated successfully, but these errors were encountered: