Skip to content
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

move pexpect-maxima code to maxima_lib #17753

Open
rwst opened this issue Feb 9, 2015 · 20 comments
Open

move pexpect-maxima code to maxima_lib #17753

rwst opened this issue Feb 9, 2015 · 20 comments

Comments

@rwst
Copy link

rwst commented Feb 9, 2015

This metaticket tracks efforts to remove the usage of pexpect for calling maxima, either by using maxima_lib or replacing it altogether. Code that is dependent on the maxima expect interface is in:

Already done:

This can be considered part of the metaticket #16688. See also http://trac.sagemath.org/wiki/symbolics/maxima

Component: interfaces

Issue created by migration from https://trac.sagemath.org/ticket/17753

@rwst rwst added this to the sage-6.5 milestone Feb 9, 2015
@rwst

This comment has been minimized.

@rwst rwst removed this from the sage-6.5 milestone Feb 17, 2015
@rwst

This comment has been minimized.

@fchapoton

This comment has been minimized.

@fchapoton

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@rwst

This comment has been minimized.

@dimpase
Copy link
Member

dimpase commented Nov 27, 2017

comment:17

I am confused about the meaning of Absolute vs Optional dependencies mentioned on the wiki, could you elaborate?

@rwst
Copy link
Author

rwst commented Nov 27, 2017

comment:18

As far as I recall, I named that code optional that I thought is only executed when certain non-default keywords are given. Looking at the three items,

  • symbolic_expression_from_maxima_string is only used in doctests of calculs.py but is absolutely imported by ex.factor() and in relation.py:string_to_list_of_solutions() which is used by solve() so the assessment was wrong
  • stirling_number2 in combinat/combinat.py: default is not Maxima, okay
  • integration/*: certainly Maxima is called, so it's wrong

Thanks for asking, I'm changing it.

@rwst

This comment has been minimized.

@dimpase
Copy link
Member

dimpase commented Jul 5, 2020

comment:20

there are places where maxima.eval instead of considerably faster maxima_calculus.eval is used for no good reason, e.g. in src/doc, see #30071.

@dimpase

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants