#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
Reporter: jpflori | Owner: burcin
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.7.2
Component: symbolics | Keywords: pynac
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-------------------------+--------------------------------------------------
Comment(by burcin):
I updated my patch-queue with some small but important fixes to the
handling of these leading minuses. Please update and try that version.
There updates were sitting on my hard disk for months, so I need some time
to remember the details again.
Replying to [comment:53 jpflori]:
> And isn't there a better way to check for leading minus than to emulate
printing (even at the cost of duplicating some code) ?
Since the coefficient can be any Sage type, I don't think there is any way
to get that information without printing. IIRC, GiNaC handles this by
defining the csgn() function appropriately, but they don't support as many
types and printing styles as we do.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9880#comment:54>
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.
