symengine VS emacs-ipython-notebook

SymEngine will do this: https://github.com/symengine/symengine

If you need programmability or interoperability, Sympy is way nicer. If you just want an interactive symbolic calculator, Maxima is fine but sometimes quirky (has odd conventions due mainly to its age). As heisig points out, Maxima can be quite a bit faster (but I run into slow things with it too). Using Maxima via Sage is in some ways the best of both worlds.

You may also be interested in SymEngine: https://github.com/symengine/symengine

Context: I'm making a application for robotics calculations, making symbolic calculations using (symengine), and at some point I would like to be able to see the steps of these calculations, symengine has a function that returns the latex code do the elements you want. So I was trying to find a library or something of sorts to render that text into an image, I'm using Dear IMGUI in the docking branch to make a simple UI where I would like to display these equations. I know it might not even exists but I would like to give it a try. I found KLateXFormula, which depends on Qt as far as I understood, so I would like to avoid that if possible, I also studied a bit about the TeXStudio repo and found they use Qt to render previews. I also tried to understand the miktex repo searching for a function that I could use, but I barely understood the structure of the repo. I'm getting frustraded. I also found approaches where people would call latex executables to parse latex to DVI(Or something like this) but I would also like to avoid this approaches if possible.

- Might there be any way to leverage the work of https://github.com/symengine/symengine ? I assume a straight-up language binding to symengine might be a completely separate project, but possibly for some specific features symengine, maybe... (It is a pity they chose c++ and not rust to implement symengine in. In the end, the main target seems python/sympy here and not c++.)

the github source : https://github.com/millejoh/emacs-ipython-notebook

I used https://github.com/millejoh/emacs-ipython-notebook at one employer and it works quite well for Jupyter. Of course Org is great but if your coworkers are unfamiliar it's probably a non-starter.

Looking at https://github.com/millejoh/emacs-ipython-notebook/issues this person seems to be using the github issues tracker as a combination of their personal tech support line + ranting board.

Maybe Emacs should have went down the road to have good Jupyter notebooks support instead, even EIN's maintainer was advising against using notebooks.

So that project was forked and this is the better location https://millejoh.github.io/emacs-ipython-notebook/

Except when it doesn't work. I tried using it a few months ago on both Windows and WSL, but I had to give up. Surprisingly, EIN¹ running a Maxima kernel worked.

I was going to try again before commenting, but I broke my WSL setup last week and didn't have time to fix it yet, but I sure will try it again next month.

¹ http://millejoh.github.io/emacs-ipython-notebook/

EIN also looks good but I haven't used it.

From my perspective when I had to turn ML models from a "real scientist" to something I could use in production, emacs-ipython-notebooks[1] was immensely helpful for me, since it allowed to connect to the jupyter server and edit and copy things from emacs to other code places as if I'm looking at an org mode file.

I see the appeal of Jupyter notebooks for someone testing out things or experimenting, but it's a bit like a brain dump that isn't that trivial to navigate around when a second or third person is involved.

[1] https://github.com/millejoh/emacs-ipython-notebook

Hey all! I'm quite attracted by the Emacs IPython Notebook (ein) package and would love to incorporate it into my workflow. However last time I tried (about a year and a half ago) it was officially unsupported in spacemacs and my experiments led to constant headaches like undotree failing, notebooks not saving, native compilation crashing, and a reliance on elpy for IDE features (afaik the only elpy layer available can be found here, uses ESS bindings, and seems to be orphaned.)