Thomas Kluyver

Yes, it should probably catch that ValueError and send it to the user as an error message. PRs welcome.

It seems like the interface between terminal emulator and shell is gradually expanding. `bash_kernel` is kind of a weird half-way house: we want less interactivity than running in a terminal...

That does look like it might be related to bracketed paste. At a guess, bash is sending the escape codes to switch bracketed paste mode on & off, but Jupyter's...

No, there's not really any way round this. It's a longstanding limitation (e.g. #60, #63, #83): the Jupyter kernel protocol expects that the kernel will actively request input it needs...

I can't think of anything already set that you could detect for this. Part of the what Pexpect does is tricking programs into using their 'interactive mode', either for testing...

It should correctly treat a non-zero exit as an error, so it will stop there if you have done 'run all', or executed it from the command line with something...

Yes, in general it doesn't work with anything that expects interactive input. There isn't a standard machine-readable way for processes running in a virtual terminal to say that they're waiting...

I'm not sure there's a good way to do that - installing the kernelspec files is something of a hack on the python packaging toolkit. E.g. I can't make wheels...

No, I don't think that would be any easier to manage. For reference, the reason it's dynamically created is so that it refers to the Python interpreter you used to...

I don't think there's any way to display HTML from bash_kernel at present. I'd be open to some generalisation of the mechanism to display images, but I don't know what...