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
Repair to totallyreal_dsage #4372
Comments
Attachment: 10736.patch.gz Attachment: 10735.patch.gz |
comment:1
Any patch should be reviewed in detail regardless of nodoctest status or not. Is there a specific reason we shouldn't remove the nodoctest on that file now? Cheers, Michael |
Attachment: 10737.patch.gz |
comment:2
Agreed. I'd say the code is still 'experimental'; it only most of the time works for me without extra effort, though this is probably because dsage itself keeps getting upgraded. What is the sage philosophy here? The code will never be used as a component in some thing else, but I thought I should still share it. JV |
comment:3
Well that will happen at most one more time, since dsage development stopped. |
comment:4
REFEREE: I applied the first two patches no problem to 3.2.1.alpha2. The third patch fails to apply:
Looks easy to fix... so I fix it. No problem. I then enable doctesting and try the tests, but they totally hang in line 60:
I delete ~/.sage/dsage and try again. Doctesting finishes with some errors:
... so I try
and try doctesting again and it hangs. Any thoughts? |
comment:5
Replying to @williamstein: I'm not sure totallyreal_dsage has ever had its doctests pass. I see some error messages are because dsage has even changed since the doctests were written. I'd like to keep this as nodoctest; it will be nontrivial to make the code easily usable to others, and yet I'd like to keep the code updated with my changes. JV |
comment:6
As of Sage 4.3.1, ticket #7975 removed dsage from the standard spkg repository. I'm closing this ticket as wontfix. If there's a need for using dsage, one could make dsage an optional package with doctests marked as optional. |
Two changes/updates to get totallyreal_dsage to work:
(1) Craig improved the totally real field enumeration, but changed the public incr() to increment().
(2) dsage had some update where wall_time of a job is returned as a datetime object.
totallyreal_dsage is still at a nodoctest status, so shouldn't require any (meaningful) review if the patch works (it's against 3.1.4).
JV
Component: number theory
Issue created by migration from https://trac.sagemath.org/ticket/4372
The text was updated successfully, but these errors were encountered: