-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Meta-ticket: Use the SymPy assumptions facility #31958
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:6
One issue with using sympy for the implementation is that loading it would add quite a bit to the start up time:
|
Here is a closely related example to #27998, though it is a bit worse, since instead of an error, you get the wrong answer. var("x,y")
assume(x>0)
assume(y>0)
print("x^2=1 and y^2=1")
show(solve([x^2==1, y^2==1], x, y))
OUTPUT:
(x, y)
x^2=1 and y^2=1
[[x == 1, y == 1], [x == -1, y == 1], [x == 1, y == -1], [x == -1, y == -1]] Then answer should be Note that sympy of course works perfectly fine for this problem, so this is a vote for this ticket:
More details: https://cocalc.com/wstein/support/assumptions/files/bug.sagews |
SymPy has a clean and general design for assumptions.
https://docs.sympy.org/latest/modules/assumptions/index.html
We should connect to it. Based on #31926 (#24171, #31931, #31938), we should be able to express everything in it that Sage's assumptions can do, so perhaps we can replace what we have in Sage completely by SymPy.
Tickets:
Symptoms:
SR
drops assumptionsCC: @egourgoulhon
Component: symbolics
Issue created by migration from https://trac.sagemath.org/ticket/31958
The text was updated successfully, but these errors were encountered: