#17254: Upgrade to Singular-4-0-2
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-7.2
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Jakob Kroeker, | Work issues:
Jean-Pierre Flori, Jeroen Demeyer | Commit:
Report Upstream: N/A | 1426ad88ab3e8a3d72a75f952727deca44f951a7
Branch: | Stopgaps:
u/jdemeyer/ticket.17254.squashed.latest|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by jakobkroeker):
Replying to [comment:183 jdemeyer]:
> It's not because Singular prints something in a certain way that Sage
has to print it that way. The correct fix is changing the way how Sage
prints Singular objects then.
At least we should understand the reasons
- for {{{ 1*x }}}
- and for braces around floats
I do not know whether it is safe to remove the {{{1*}}} and the braces
around floats.
I don't know what Sage does for example with {{{_repr_()}}}, (which calls
{{{singular_polynomial_str()}}} which in turn calls {{{p_String}}}
And if it' safe, how we should do that?
regexping each polynomial string on the fly?
--
Ticket URL: <http://trac.sagemath.org/ticket/17254#comment:186>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
