-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Improve doctest coverage for sage.rings.qqbar #12662
Comments
Attachment: trac_12662-qqbar-doctest.patch.gz Patch against 5.0.beta7 |
This comment has been minimized.
This comment has been minimized.
Author: David Loeffler |
comment:1
Here's a patch which gets full doctest coverage. |
comment:2
Can't we just get rid of this stuff? If anyone misses it, it's in the mercurial history.
|
comment:3
The functions Also I do think they make mathematical sense. A field is generated by a single element, the 1 of the field, and for a homomorphism of fields we must send 1 to 1. |
Work Issues: uncomment generators methods |
comment:5
All right, I'll put them back in. |
Apply only this patch. Patch against 5.0.beta10 |
Changed work issues from uncomment generators methods to none |
comment:6
Attachment: trac_12662-qqbar-doctest-v2.patch.gz Here's a new patch which adds doctests for these routines instead of commenting them out. |
Work Issues: doctest failure |
comment:7
I applied this to beta10, running OSX 10.6.8, and got the following two failures:
|
comment:8
Dear JStarx, I strongly suspect you applied the patch and ran "sage -t" without running "sage -b" first, which gives exactly these two errors. (They come from the two non-docstring changes in the patch: I renamed Can you run "sage -b" and then do the test again? |
Changed work issues from doctest failure to none |
comment:9
Yup, silly mistake. All the tests pass. It's getting late, but when I get some time this week I'll finish reading through the diff and review it. |
comment:10
Ok, it all looks good. The only minor tweek I would make is to delete the commented stuff on lines 7594 - 7641. Not sure why that's there or why we wouldn't delete it. Anyway, I'm gonna set it as a positive review. If you agree that that commented stuff can be deleted then feel free to keep the ticket marked as a positive review after deleting it. |
Reviewer: Jim Stark |
Merged: sage-5.0.beta11 |
... from its current abysmal 45% (112 of 244) to something a bit more respectable.
Part of the meta-ticket #12024. See also #12665 (a bug discovered in working on this ticket).
CC: @sagetrac-JStarx
Component: doctest coverage
Author: David Loeffler
Reviewer: Jim Stark
Merged: sage-5.0.beta11
Issue created by migration from https://trac.sagemath.org/ticket/12662
The text was updated successfully, but these errors were encountered: