#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: symbolics | Keywords: pynac
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------+--------------------------------------------------
Comment(by kcrisman):
> I don't use everything pynac provides so it is more than probable that
some expression are not correctly printed now.
>
> Do not hesitate to report it.
I'd like to test this at some point, but have two problems.
- There is too much C++ for me to review it properly, unless a lot of it
really is just reverting. Is there an easy way to figure out what is
actual new code, and what is going back to something more-or-less Ginac?
- I am not sure exactly what sort of expressions would not be properly
printed. Can you give any kind of example of what sort of bad behavior to
look for with testing (perhaps randomized)?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:9>
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.
