Antonio Cuni

> ### Exceptions in Display Should Show Up Onscreen > I'd propose that if an object fails to render (e.g. if an exception is raised when processing the object through...

**EDIT**: this is wrong, nevermind :man_facepalming: @marimeireles you closed this as completed but it's not true :) `print()` still displays something in the DOM, while it shouldn't. Try to run...

Sorry, I made a mistake and I was running pyscript on the wrong branch. I confirm that this issue is fully resolved, closing it again.

Good catch. This happens because `sys.stdout` is actually an `OutputCtxManager`: https://github.com/pyscript/pyscript/blob/bc4581d9e50286f0463285f13c015e487831fa0e/pyscriptjs/src/pyscript.py#L370-L393 It lacks many attributes/methods which are normally present on `sys.stdout`, e.g. `.fileno()`, `.flush()`, `.encoding`, etc. As a temporary workaround,...

I think it's a very good idea. I also agree with Mariana that #264 is the way to go, so probably we should just improve it (or merge it and...

> Should we move the examples to https://github.com/pyscript/pyscript-collective? this might be a good idea. We could write that the main `pyscript` repo is ONLY for people who wants to modify...

> What I've been thinking about the examples for a while now (and that's part of the reason we started the collective, thanks Madhur) is that the examples we're using...

> I think that all makes sense. If we had proper tests that made show examples worked properly instead of simply loaded at all, then pointing them to latest would...

> My personal opinion is that examples should serve as display of the basic functionality of the latest released of the framework to end users. For this reason (in order):...

re @pww217 > If it makes more sense, I don't think it would be that hard to hardcode the examples to use local files and then point them to pyscript.net...