jupyter_console VS stack_data

Sounds like you'd be interested in jupyter-console, which lets you do something like ilua for any language that has a Jupyter kernel. Well, in theory; the one language kernel I use that would really benefit from it, F# (which has a pretty shit command-line repl) doesn't work correctly. It's flawless with the OCaml kernel, but there isn't much point to running that one on the terminal considering utop is insanely good already.

You likely want to use something like https://github.com/jupyter/jupyter_console, or ipykernel directly to have a persistent python process. One issue is that shells are text based, so you have to do a lot of serialisation/deserialisation.

But honestly at that point I would just look into https://xon.sh/ that blends Python and Shell together. IPython and Xonsh devs are friends, so if you need anything from one into the other it's likely doable.

- https://github.com/alexmojaki/cheap_repr (not a debugger, but used by the above two as well as directly by futurecoder)

Tracebacks:

- https://github.com/alexmojaki/stack_data (this is also what powers the new IPython tracebacks)

AST in a more general concept see https://en.wikipedia.org/wiki/Abstract_syntax_tree, it basically turn your text into a tree where f(a) + f(b) is `call(plus, call(f, a), call(f,b))`. Using https://github.com/alexmojaki/stack_data we can say "the error occurred in `a`, while trying to call `f`, while calling `plus`, get the range in the original text and make them yellow.