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
Get Maxima to easily accept flag values #10955
Comments
comment:1
Works for me on some flavour of 5.13.beta0
I didn't check if the answer makes sense, but at least setting the flag has effect. |
Author: Peter Bruin |
Branch: u/pbruin/10955-maxima_radexpand |
comment:2
Works for me too; here is a doctest. |
Commit: |
Reviewer: Nils Bruin, Karl-Dieter Crisman, Michael Orlitzky |
comment:3
As far as I can tell this is fine. I have no idea why this didn't work before. Passes tests, does right thing. Wow, I am just now noticing that the suggestion made earlier was pretty bogus.
Totally not the same thing as
which also happens to be affected by |
Changed reviewer from Nils Bruin, Karl-Dieter Crisman, Michael Orlitzky to Nils Bruin, Karl-Dieter Crisman |
Changed branch from u/pbruin/10955-maxima_radexpand to |
Maxima relatively recently decided that 1/sqrt(x) is not sqrt(1/x), for good reasons (1/sqrt(-1)=-i but sqrt(1/-1)=i in usual discussion). So for the following integral, they note that it depends on how you input it:
Fine. Then they suggest using the flag
radexpand:all
to make the first one behave. But I can't figure out how to get it to evaluate.Trying maxima.eval only changes that I get 'all' instead of all. We should make this work, since this is the calculus instance of Sage!
CC: @robert-marik @burcin @nbruin @jasongrout @wdjoyner
Component: calculus
Keywords: maxima, flag, radexpand
Author: Peter Bruin
Branch/Commit:
b94b48a
Reviewer: Nils Bruin, Karl-Dieter Crisman
Issue created by migration from https://trac.sagemath.org/ticket/10955
The text was updated successfully, but these errors were encountered: