#12261: Bring Doctest coverage for element_ext_pari.py to 100%
-----------------------------------+----------------------------------------
Reporter: roed | Owner: mvngu
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: doctest | Keywords:
Work_issues: raise!=Raise | Upstream: N/A
Reviewer: Karl-Dieter Crisman | Author: David Roe
Merged: | Dependencies:
-----------------------------------+----------------------------------------
Changes (by kcrisman):
* cc: robertwb (added)
* status: needs_review => needs_work
* work_issues: commit message, PARI (maybe?) => raise!=Raise
Comment:
As I suspected, changing `raise` to `Raise` would cause problems.
{{{
./sage -b
<snip>
SyntaxError: invalid syntax (element_ext_pari.py, line 653)
Error importing ipy_profile_sage - perhaps you should run %upgrade?
WARNING: Loading of ipy_profile_sage failed.
}}}
I don't mind you removing that function! I just don't know what it does
or why it can now be removed - actually, upon reading it, it does make
sense. If someone else (e.g., robertwb) can verify that the same
functionality of checking that two such elements come from the same finite
field is in Sage, I am very happy with reducing our doctest needs by
removing that.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12261#comment:6>
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.
