#12375: submit a giac spkg
-------------------------------------+-------------------------------------
Reporter: frederichan | Owner: tbd
Type: enhancement | Status: needs_work
Priority: minor | Milestone: sage-6.4
Component: packages: | Resolution:
optional | Merged in:
Keywords: giac | Reviewers:
Authors: Han Frederic | Work issues:
Report Upstream: N/A | Commit:
Branch: public/giac_spkg | 9562050fcc8774cbfeeaa88479cd8eb5733a45a7
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by frederichan):
Yes I can reproduce all these diffs outside sage so it is not a problem of
the spkg. For the loss in precision I have reported it on xcas forum to
know if it is a long term change or a bug so I wait a little to know if it
should be changed in giac.py.
But I have also looked at the cython interface and I found a problem that
I didn't have with sage 5.11.
in the .pyx module I did:
{{{
cdef extern from "csage/interrupt.h":
void setup_sage_signal_handler "setup_sage_signal_handler"()
setup_sage_signal_handler()
}}}
and it worked fine with sage 5.11. But with my sage 6.2, even if I do this
in an empty module tutu.pyx, then after doing in sage:
{{{
import tutu
}}}
hitting a control-c in the prompt quits sage. Is there some way to set the
good signal handler for interruptions?
--
Ticket URL: <http://trac.sagemath.org/ticket/12375#comment:46>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
