#16025: Calling the .n() method on reals shouldn't increase precision
-------------------------------------+-------------------------------------
Reporter: rws | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: calculus | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/16025 | d4bdfcab040c79a63125695de8835e875ca9c236
Dependencies: #17166 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:12 kcrisman]:
> Somehow I feel like there should be more documentation where the
examples have disappeared.
I assume you refer to the 2 examples in
`src/sage/modules/free_module_element.pyx`? They were testing the `.n()`
method for vectors, but there are already plenty of tests for that (also
in `src/sage/misc/functional.py` for example).
--
Ticket URL: <http://trac.sagemath.org/ticket/16025#comment:14>
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.
