#12730: Stopgap for #8862
----------------------------+-----------------------------------------------
Reporter: roed | Owner: burcin
Type: defect | Status: new
Priority: blocker | Milestone: sage-5.0
Component: calculus | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------+-----------------------------------------------
Comment (by roed):
Stopgaps are implemented by just showing a warning to the user (but only
the first time that a warning for a given ticket would be triggered). At
whatever point in the code where it's appropriate, you call stopgap. See
#12691.
I would also like to avoid displaying a warning every time the user calls
solve. But the point of stopgaps is to warn the user when they're doing
something that might yield known incorrect results, and point them to a
trac ticket where the issue is discussed. I'm not sure what the right
solution is here though.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12730#comment:2>
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.
