Carsten Allefeld

The problem seems to be related to `MatlabKernel._execute_async`. An extremely hacky workaround is to comment out the import of `pipes` from `wurlitzer` in `kernel.py`: ```python # try: # from wurlitzer...

Dug a little deeper: The problem is caused by a bug in the Matlab engine for Python: https://github.com/mathworks/matlab-engine-for-python/issues/34

I was looking for this feature, missed it, and then found this issue. As far as I can tell, right now `Color` objects represent alpha, but don't do anything with...

quoting myself from #7876 "interface to manage workspaces": > Under the URL `/lab/workspaces` without an appended workspace name, an interface to manage workspaces should be shown. that is: > >...

@afshin, I thought it would be the logical way to do it, but I understand.

> I think the best option for placement of a workspace management UI is actually in the launcher. Since workspaces change the URL, open files, and arrangement of tabs, the...

So far I have only encountered the error if using `jupyter console --kernel`.

I found a solution: I was able to detect the execution of an instruction to shut down the interpreter, *but only afterwards*, because the Python interface to the interpreter throws...

@jjvraw, I have implemented `do_shutdown`. But as the docstring says, this is "to do things when the frontend shuts down the kernel", i.e. cleanup actions. I'm looking for a way...

@martinRenou > What you can do is kill the process yourself from code though. According to the messaging protocol it's considered a valid shutdown if the user typed "quit" in...