Hi!

The following is a problem that was observed with trac ticket #11431
on the build bots mark and t2: The line
    singular.eval('ring r1 = (9,x),(a,b,c,d,e,f),
(M((1,2,3,0)),wp(2,3),lp)')
fails with the patch from the ticket.

However, the ticket does not change how a string is interpreted/
executed in Singular - it only affects how stuff in Singular (such as
lists, ideals and strings) is translated into the corresponding object
in Sage.

So, I wonder whether the failure was caused by the patch, or whether
it just accidentally revealed an existing bug by a new doc test.

I currently have no new Sage version on my t2 account. Can please one
of you with a recent Sage version test it on t2 or mark?

It would also help if someone could remind me how to build Sage on t2
on my own. Then, I could test it myself...

Best regards,
Simon

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to