New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A wrong (easy) limit #10868
Comments
Changed author from jvarona to none |
Upstream: Reported upstream. Little or no feedback. |
comment:1
This is in Maxima.
This is still present in the latest Maxima. See this report. |
comment:2
This report suggests it is fixed in the latest upstream. This would need a patch to verify, once we would update Maxima to that release. |
Changed upstream from Reported upstream. Little or no feedback. to Fixed upstream, but not in a stable release. |
Dependencies: #12094 |
Changed upstream from Fixed upstream, but not in a stable release. to Fixed upstream, in a later stable release. |
comment:3
This is fixed in stable maxima 5.24.0:
|
Attachment: sage-trac_10868.patch.gz Add a doctest for this result. Apply on top of #11483 and #11591 to avoid fuzz. |
Author: Michael Orlitzky |
Reviewer: Aly Deines |
Merged: sage-5.0.beta3 |
If we define f(n)=2+1/factorial(n) the answer of sage for limit(1/f(n),n=oo) is 1, that is clearly wrong. However, limit(f(n),n=oo) gives the answer 2, that is correct.
I have seen this problem in (at least) sage 4.6 and sage 4.6.2, in several kind of computers.
Depends on #12094
Upstream: Fixed upstream, in a later stable release.
CC: @orlitzky
Component: calculus
Author: Michael Orlitzky
Reviewer: Aly Deines
Merged: sage-5.0.beta3
Issue created by migration from https://trac.sagemath.org/ticket/10868
The text was updated successfully, but these errors were encountered: