-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Consider using Mathematica syntax for integration #1221
Comments
comment:1
I changed this to sage-2.9, since it will be very easy to implement. |
comment:2
|
comment:4
This will break backward compatibility in a massive way, so I would suggest setting it to "won't fix". Cheers, Michael |
comment:5
Well, I haven't replied here when you suggested won't fix, as I was thinking about this. I understand that breaking code is bad. But still consistency is consistency. There are ways to improve the API in a non compatible way, e.g. introduce both versions and raise python warning for the old API. and after couple releases, remove it. Also this was agreed on the sage-devel, so if you seek a different conclusion, you should (imho) advocate that on the list. |
comment:6
See also #2787. |
comment:8
I suggest we close this ticket since we now support the suggested syntax:
The docstring for Further discussion on
Comments? |
comment:9
I think so, the one-variable issue is resolved and the double integrals are covered in #2787 |
comment:10
I'm closing this as fixed. See comment:8 for more info. |
I think we should use this syntax for integration:
instead of
as in SAGE currently, to be close to Mathematica. Because then you can
use the syntax:
integrate(cos(x*y), (x, -pi/2, pi/2), (y, 0, pi))
for multiple integrals.
See also [1], how we discussed this in SymPy.
[1] http://code.google.com/p/sympy/issues/detail?id=25
CC: @jasongrout
Component: calculus
Issue created by migration from https://trac.sagemath.org/ticket/1221
The text was updated successfully, but these errors were encountered: