#11431: Conversion from Singular to Sage
---------------------------+------------------------------------------------
    Reporter:  SimonKing   |         Owner:  was            
        Type:  defect      |        Status:  needs_info     
    Priority:  major       |     Milestone:  sage-4.7.1     
   Component:  interfaces  |    Resolution:                 
    Keywords:              |   Work_issues:                 
    Upstream:  N/A         |      Reviewer:  Martin Albrecht
      Author:  Simon King  |        Merged:                 
Dependencies:  #11316      |  
---------------------------+------------------------------------------------

Comment(by SimonKing):

 I was able to build sage-4.7.1.rc1 on mark (which is supposed to be
 identical with mark2). It turns out that the bug was not ''introduced''
 but ''revealed'' by my patch.

 With the freshly built Sage-on-mark, I get
 {{{
 sage: singular.eval('ring r1 =
 (9,x),(a,b,c,d,e,f),(M((1,2,3,0)),wp(2,3),lp)')
 ---------------------------------------------------------------------------
 RuntimeError                              Traceback (most recent call
 last)

 /home/simonking/SAGE/sage-4.7.1.rc1mark/<ipython console> in <module>()

 /home/simonking/SAGE/sage-4.7.1.rc1mark/local/lib/python2.6/site-
 packages/sage/interfaces/singular.pyc in eval(self, x, allow_semicolon,
 strip, **kwds)
     548
     549         if s.find("error") != -1 or s.find("Segment fault") != -1:
 --> 550             raise RuntimeError, 'Singular error:\n%s'%s
     551
     552         if get_verbose() > 0:

 RuntimeError: Singular error:
    ? cannot open `gftables/9`
    ? cannot make ring
    ? error occurred in or before STDIN line 25: `ring r1 =
 (9,x),(a,b,c,d,e,f),(M((1,2,3,0)),wp(2,3),lp);`
    ? expected ring-expression. type 'help ring;'
 }}}

 The question is: How shall we proceed? Removing that particular test would
 be a shame, since it shows that my patch can manage to parse pretty
 complicated stuff. Perhaps it is  possible to simplify it, so that it is
 still complicated, but works on mark and t2.

 In either case, I will report on sage-solaris, and probably will file a
 bug report to the Singular team as well.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11431#comment:13>
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.

Reply via email to