Utensil

There's one failed test under Python 3 which is not expected (it works locally), but all failures under Python 2.7 are expected because the original implementation from abrombo didn't consider...

I finally read the gist and find it quite neat. One concern, should we use the private `_sympifyit`?

If we're going to use private methods (as an important design dependency) in SymPy, it's better to bring the discussion to SymPy and possibly submit PRs to make it part...

I believe the equivalence of this is happening already, only in a different approach: https://github.com/pygae/galgebra/commits/master/galgebra/atoms.py . Should we close this? @eric-wieser

> The point is to have one piece of code produce either LaTeX or plaintext output, without having to change anything Yes, I strongly agree that this is the core...

I'll go for call-super-and-finetune, trying that locally now.

``` ==================================================================================== short test summary info ==================================================================================== FAILED examples/ipython/dop.ipynb::Cell 2 FAILED examples/ipython/dop.ipynb::Cell 5 FAILED examples/ipython/dop.ipynb::Cell 6 FAILED examples/ipython/dop.ipynb::Cell 7 FAILED examples/ipython/dop.ipynb::Cell 8 FAILED examples/ipython/colored_christoffel_symbols.ipynb::Cell 16 FAILED examples/ipython/colored_christoffel_symbols.ipynb::Cell 17 FAILED examples/ipython/colored_christoffel_symbols.ipynb::Cell...

> I'll go for call-super-and-finetune, trying that locally now. I gave up on this approach, it's even worse than what we have for now: after calling super, we have only...

> It has no commits pushed to it though. Oh, the local code is so ugly that I haven't pushed it. Forget about it then.

I never noticed this part of code.......