Andrea Giammarchi

none of this is an issue anymore as current PyScript lands as regular ECMAScript module. ```html ``` Here the latest docs: https://pyscript.github.io/docs/2023.11.2/beginning-pyscript/ P.S. you can also map `@pyscript/core` as `https://pyscript.net/releases/2023.11.2/core.js`...

Current PyScript encourages the usage of `` which grants a `target` and doesn't suffer any Custom Element issue so I think we can close this but feel free to re-open...

I believe these discussions should be moved to https://github.com/pyscript/docs

Current PyScript encourages the usage of `` instead of `` with the advantage that a *script* tag is designed to be a data-block and nothing in there is parsed from...

Current PyScript forwards errors to the main thread but also it bootstraps in a completely different manner. This bug is not relevant so I am closing this. Feel free to...

This is not actionable for us, it's a standard behavior that can be easily fixed via CSS as previously suggested. Closing as there's no issue to fix (we can't transform...

Closing as half duplicate of https://github.com/pyscript/pyscript/issues/1050 where once that's done nobody would need an API but because the PyDom API progress is not shared in here I think at least...

I am not sure why semver or any other versioning would solve the inherent issue described in here, but that decision has been made and we still land on CDN...

Hopefully RequireJS is not used much anymore but right now PyScript is a standard ECMAScript module so this issue does not exist anymore.

We solved the input issue in current terminal when it runs in workers and from a *sync* perspective there's nothing else one can do on the main thread because it...