#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.2
Component: symbolics | Keywords: pynac
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------+--------------------------------------------------
Comment(by jpflori):
The problem is not the GiNaC original internal order (even if
http://www.ginac.de/reference/structGiNaC_1_1expair__rest__is__less.html
states it is not a SWO... at least using it makes the bug disappear and
inconsistencies in automatic simplifications disappear; if it does not
work, i guess it should be fixed by GiNaC team) but the modification of
that order used in pynac (and so in Sage).
AFAIK the two patches here are still necessary, the segfault disappeared
(!?!) but i still get some problems with automatic simplification as shown
in http://trac.sagemath.org/sage_trac/ticket/9880#comment:15.
- the first patch (by Burcin) reverts the original GiNaC ordering for
internal use (e.g. to be used in call to std::sort) in pynac and use the
modified order only for printing (it should also be uesd at some point for
operands access and so on).
- the second one (by me) should be applied on top of the first one and
tries to polish the order used for printing so that is looks more like
degrevlex.
It should not be much more difficult to implement other orders for
printing (and operands access).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:19>
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.
