-
-
Notifications
You must be signed in to change notification settings - Fork 504
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
Assumption bug of positive symbolic variable #21923
Comments
Changed keywords from none to days79 |
This comment has been minimized.
This comment has been minimized.
comment:2
double floating problem?
|
comment:3
|
comment:5
It is well known that there is no reasoning capability in Sage. See for example this thread: https://groups.google.com/d/msg/sage-support/AiPtd0x52kQ/WeOmvlFCEAAJ The |
comment:6
See also #19162. |
comment:7
Yes, this is already in Maxima:
Now I see that http://maxima.sourceforge.net/docs/manual/maxima_11.html#assume mentions Should the milestone of this ticket be changed to sage-duplicate or to sage-wishlist? |
comment:8
I think it's a duplicate of the enhancement ticket #19162. |
comment:9
BTW for an overview of existing symbolic tickets please see https://trac.sagemath.org/wiki/symbolics |
comment:10
I am not sure such tickets should be closed like that. Indeed, compared to #19162, there is a concrete use case (a bug), so it is important to keep track of it in the doctests, even if the fix comes from another ticket. At least, we have to copy the doctest on the other ticket, in order not to lose it. |
comment:11
still reproducible in 9.5.beta7 |
There is an easily reproducible bug with assumptions:
The same happens for
var("p")
and then assumingassume(p>0)
. The following list should be[0..999]
, but we see something different:CC: @rwst
Component: symbolics
Keywords: days79
Issue created by migration from https://trac.sagemath.org/ticket/21923
The text was updated successfully, but these errors were encountered: