#16651: NumberField to SymbolicRing: rational but still approximate
---------------------------------+------------------------
Reporter: gagern | Owner:
Type: defect | Status: new
Priority: critical | Milestone: sage-6.3
Component: number fields | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+------------------------
Changes (by gagern):
* cc: kcrisman (added)
Comment:
Cc-ing kcrisman since his commit
[http://git.sagemath.org/sage.git/commit/?id=3278794b9a63e706b9ccef52435575a79f9a64ce
3278794] for #6642 introduced the use of `to_poly_solve=True` for
`NumberFieldElement`, without any example of when this might be of use.
Can you give an example of when this would be useful?
I've written code for #14239 to suite my perceived needs there. Including
a fallback from `to_poly_solve=False` to `to_poly_solve=True` for which I
don't have a test case either. It might turn out that we went very similar
things in both these places, and we want to factor them out into some
common function. For the moment I felt that having separate code might
increase chances that my code gets a positive review, since new code is
less likely to break expectations than tinkering with existing code.
--
Ticket URL: <http://trac.sagemath.org/ticket/16651#comment:1>
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.
