Implement REPL with Python stdlib code and codeop

[brandonwillard]

What do you think about using code and codeop to implement the basic REPL mechanics?

[gilch]

That might be cleaner. I'm not sure how to do it though. The doctests are also closely tied to the REPL. I'm wondering how much they can or should hook into it.

[brandonwillard]

I'll look into it quickly.

[gilch]

The REPL could maybe use a startup banner too.

[gilch]

The sybil/doctest setup is in conftest.py, btw.

[brandonwillard]

Should we turn this into "Make a Jupyter kernel for Hissp" instead?

Some links:

• Making kernels for Jupyter
• Making simple Python wrapper kernels
• A simple example kernel for Jupyter

[gilch]

No we shouldn't. It is a goal of Hissp proper to have no dependencies. (This restriction does not apply to its tests, which need not be distributed in the hissp package.) The basic included REPL should use only the standard library.

We can certainly have a Lissp REPL based on IPython, but it must live in a separate repository, or at least be released as a separate package on PyPI. It will have independent releases and version numbers from Hissp itself. Which means we still need a basic one to include with Hissp.

Hebigo, on the other hand, does not share this goal. I'm fine with that only having an IPython REPL to start as well as reasonable dependencies.

[brandonwillard]

Ah, yeah, then change it to ”Start a Project for a Hissp Jupyter Kernel".

[gilch]

Rather than change this issue to the Kernel, we can add that as a separate issue. The original point of using the stdlib code/codeop may still be a good idea for the included basic REPL.

[gilch]

I think the InteractiveConsole-based REPL from #62 is pretty good now.