Read-only forum archive

Upgrading Singular to 3-1-7 in Sage

Upgrading Singular to 3-1-7 in Sage

jpflori · Fri Oct 24, 2014 1:43 pm

Dear all,

We're having trouble moving from Singular 3-1-6 to 3-1-7 in Sage.
See (link not allowed...) trac.sagemath.org/ticket/17184.
Any idea of wht's going on?

(We're aware 4-0-1 is out, but that would require more work, or so we thought.)

Thanks in advance for your help,
JP

Re: Upgrading Singular to 3-1-7 in Sage

hannes · Sat Oct 25, 2014 4:06 pm

One problem may be found in rKill (Singular/ipshell.cc, line 5436-5441).
When the current base ring is removed (for example, if it was a local variable
of a procedure we now leave) it is checked if this ring is used anythere else
and if not, currRing is set to NULL.
This is fine in Singular but can be a bad idea if currRing comes from outside Singular. It may help to remove this test as it is not really needed.
See https://github.com/Singular/Sources/commit/2202f91f6024f7fb401cf57d7b9e656a2ea05444

Re: Upgrading Singular to 3-1-7 in Sage

jpflori · Mon Oct 27, 2014 1:17 pm

Thanks for the hint.
It does not seem to change the situation within Sage though..

Re: Upgrading Singular to 3-1-7 in Sage

jpflori · Mon Oct 27, 2014 5:19 pm

But I think I got what was wrong in the Sage code calling functions from Singular!

Thanks for the support,
JP