#16127: Fix comparison of PARI objects
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: defect | Status: new
Priority: critical | Milestone: sage-6.4
Component: interfaces | Resolution:
Keywords: pari comparison | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/pbruin/16127-gcmp | a119b00099787f5cb8c3cc8477119184e16806ee
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:5 pbruin]:
> Maybe it is better to write a variant of `gcmp_sage()` that calls
`gcmp()` and catches errors using PARI's `pari_CATCH` and `pari_TRY`
macros so that we don't have to raise Python exceptions.
If you do this, I would prefer to see this function in the PARI library
(call it `gcmp_any()` for example). Hopefully, this can be done in a way
which is acceptable for upstream.
--
Ticket URL: <http://trac.sagemath.org/ticket/16127#comment:7>
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.
