#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.7
Component: symbolics | Keywords: pynac
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-------------------------+--------------------------------------------------
Comment(by burcin):
Please excuse my ignorance, especially since I promised to make a pynac
release which includes this patch ages ago, but I have a few questions and
not enough time to test this and find out the answers on my own:
* doesn't this require a patch to the Sage library at least to fix
doctests? Is the new printing order exactly the same as the old
(inconsistent) one?
* Don't we also need to modify the operand access functions (at least the
one in Sage - not the .op() function of ginac) to return the operands in
the sorted order, not the stored (somewhat random) order?
BTW, Jean-Pierre, I wouldn't mind at all if you want to cut the new pynac
release yourself. I can provide instructions on how to do this.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:36>
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.
