4 ms·

I think that is pretty much the goal of pyscript: https://github.com/pyscript/pyscript/blob/main/docs/tutorials/getting-started.md https://github.com/pyscript/p

• bryanrasmussen 4y ago
  reimplementing/proxying the entire set of browser APIs would mean such things as DOM, the CSSOM, the browser specific JavaScript APIs, the SVGOM, the accessibility tree and probably a few other things I'm not thinking of at the moment, so a lot more than just JavaScript being understandable by Python. However I suppose it could be done with Ghost.py or similar library?
• lucideer 4y ago
  That project looks very cool - definitely a good starting point if you want to achieve this as a proof-of-concept at least, as that project looks very advanced & mature. I didn't say it wasn't possible. It's just going to be inefficient, high-maintenance and have a steep learning curve. > + the entirety of the python ecosystem Worth noting: you would only be able to use "self-contained" or "pure" libraries from the python ecosystem; any Python-only APIs in use for IO won't translate to a browser environment (or will need explicit re-implementation to map them to something different). It's essentially about learning the difference between IO API surface (DOM/W3C web APIs -vs- Python File IO/networking/etc.) and language syntax (PEP vs ECMA). Syntax translation is the (relatively) easy part - API mapping is a massive moving target, as well as an added learning curve for programmers using your system.