Follow-up from "Resolve "Thebe Lite support (experimental)""

The following discussion from !7 (merged) should be addressed:

• @rstular started a discussion: (+2 comments)

  I'd personally invert this check, as there are some ancient systems out there which alias python to Python 2. With python3, it's unambiguous that we will be running a newer python version.

added IT label

assigned to @mguichard

added Thebe label

changed milestone to %Thebe functionality Phase 1

Additionally, I've been experimenting with Thebe a bit. With the current setup, it seems like the executed cell output doesn't get rendered properly to the page?

E.g. when an error occurs, I don't think the event gets handled anywhere, besides it just being dumped into the console.

I'm guessing a thebelab.on("error", () => {...}) callback should be set up?

What kind of behaviour do you expect here?

Some sort of feedback that execution failed. Unless I'm missing something on my end, the console is the only feedback that indicates something went wrong.

Oh, I see. But that looks like a FS error, not exactly one caused by Python. In that case, it's not directed to the page automatically. Haven't encountered this one before, do you have steps to reproduce it?

Opening a non-existent file (using pandas). Third cell on this page.

Additionally, similar things happen with the second cell - import fails, but the error is only logged to the console. Adding an error callback enables us to intercept the error, but I'm not really sure how to display the output on the page.

The errors are actually being displayed, but two cells down! So, we don't have to do any manual callback stuff, but I have no clue why this is happening :/

Also, the "magic constant" used in the mknod call - 33206 - is 0o100666 in octal notation, which indicates unix permission flags.

Yeah you're probably right. The Emscriptem FS is likely modeled after Unix, but I called it magic because I found it by hooking one of the FS functions.

marked the checklist item @rstular started a discussion: (+2 comments) as completed

The follow up has been addressed in !24 (merged)

closed