#11401: magma mode in 4.7 notebook broken
----------------------------+-----------------------------------------------
Reporter: nbruin | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: interfaces | Keywords: magma notebook interface
Work_issues: | Upstream: N/A
Reviewer: Marco Streng | Author: Nils Bruin
Merged: | Dependencies:
----------------------------+-----------------------------------------------
Comment(by nbruin):
Replying to [comment:10 mstreng]:
> Why are you changing the example for "Verify that trac 9705 is fixed"? I
don't see why one is better than the other.
Because the example without newlines runs OK both with and without the fix
of #9705, so the test is not verifying any change in behaviour. The
problem described in #9705 arose when one magma statement was spread over
multiple lines and one line was passed over stdin and another line via a
"load" command. Without newlines, such splits wouldn't occur anyway.
If people can't find a fix for the "\n" in the tests, I guess we could
write it in the following way:
{{{
sage: import commands
sage: newline=commands.getoutput("echo; echo")
sage: command=(
"_<x>:=PolynomialRing(Rationals());"+newline+
"repeat"+newline+
" g:=3*b*x^4+18*c*x^3-6*b^2*x^2-6*b*c*x-b^3-9*c^2 where
b:=Random([-10..10]) where c:=Random([-10..10]);"+newline+
"until Roots(g) ne [];")
sage: magma.eval(command)
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11401#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
