#15386: Maxima is confused about limits at infinity
-------------------------------------+-------------------------------------
Reporter: ddrake | Owner:
Type: defect | Status: positive_review
Priority: major | Milestone: sage-6.3
Component: symbolics | Resolution:
Keywords: maxima limit | Merged in:
Authors: Karl-Dieter | Reviewers: Travis Scrimshaw
Crisman | Work issues:
Report Upstream: Fixed upstream, | Commit:
in a later stable release. | b6657b95ff01453ef73afb8e5390840f9cc314f2
Branch: | Stopgaps:
u/kcrisman/limit_fix_doc_15386 |
Dependencies: #13973, #11894, |
#13712 |
-------------------------------------+-------------------------------------
Comment (by kcrisman):
Thanks. The problem is that I don't know how to base things on other
tickets. I'm very naively following
[http://www.sagemath.org/doc/developer/manual_git.html#pushing-your-
changes-to-a-ticket the developer guide]. I finally figured out how to do
this efficiently with Mercurial queues only a year or two before the git
switch, so now it will take time to figure this out... No, you are right
that the only reason they "depend" on the other tickets is because of this
queue-like thing I did.
I do think the minimalist solution would be confusing for testers, because
ideally one would want to check out a branch and have it "Just work".
This was what I ran into while testing #13712. :-(
--
Ticket URL: <http://trac.sagemath.org/ticket/15386#comment:11>
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.
