-
-
Notifications
You must be signed in to change notification settings - Fork 601
symbolic.limit wrongly gives ZeroDivisionError #15451
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
Comments
comment:5
Still there in 6.6. |
comment:6
I don't understand the issue. In case of
|
comment:7
Well, it's similar to |
comment:8
The expression of which limit is evaluated in this case is |
comment:9
So you agree it's user error? |
comment:10
Replying to @rwst:
Yes. |
comment:11
I agree as well that it is a user error (sorry, I didn't see this (the wrong parentheses) when opening the ticket). Feel free to insert your name(s) in the author field. |
Reviewer: Daniel Krenn |
Author: Akshay Ajagekar |
comment:13
Actually, there are no authors if there is no patch, but definitely this is a contribution so I put it in reviewers. |
Changed reviewer from Daniel Krenn to Daniel Krenn, Akshay Ajagekar |
Changed author from Akshay Ajagekar to none |
We have
but
Those two should give the same result (at least the docstring of
x.limit
saysSee "sage.calculus.calculus.limit"
, so it has the appearence that the same functions are called).CC: @kcrisman
Component: symbolics
Keywords: symbolic, limit, wrong, zero division
Reviewer: Daniel Krenn, Akshay Ajagekar
Issue created by migration from https://trac.sagemath.org/ticket/15451
The text was updated successfully, but these errors were encountered: