Pyodide Success Story #1907
Replies: 1 comment 5 replies
-
Thanks for sharing, @alynch4047 ! Good to hear that!
Actually it might be helpful to share the process. I also wanted to explore at some point how to do a browser extension with Pyodide and that part seemed tedious. People would likely be interested in it. We likely can't put this in the docs, as things on the browser side change occasionally and it would take effort to keep up to date. However maybe this could work as a blog post? We were considering to create a Pyodide blog #1766. In case you are interested in writing a blog post about your experience (I can help with editing/review), we can certainly move forward with that. Or if you prefer another platform that's fine too. |
Beta Was this translation helpful? Give feedback.
-
Hi all I just wanted to share how Pyodide has really benefited me. I have a medium sized python project that parses a fairly complex piece of json data in order to construct another complex data structure. This functionality needs to be accessed from a Chrome extension and is (was) being served via a flask server. I've been thinking about how to distribute the python based functionality and had created a docker image for that, when I realised I could try using Pyodide to actually host and run the python from inside the browser/extension (not as a server but directly accessing the api). It took a couple of days fighting with Chrome extensions and security policies (had to drop back to Manifest v2 to allow the web assembly to run, this is a known issue in Chrome extensions CSP stuff) but got Pyodide to run my parser within the browser extension! Even better, it subjectively seems to run as fast as the externally hosted version. The whole piece of functionality is now entirely provided and hosted via the extension itself. Thanks to all who contributed to Pyodide.
Beta Was this translation helpful? Give feedback.
All reactions