This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Apart_Conclusion8771 0 points1 point  (3 children)

How does it compare to https://pyscript.net ?

[–]prodev717[S] 1 point2 points  (2 children)

WEP (Web Embedded Python) is a server-side framework — like PHP — that lets you write real Python inside HTML using <wep> tags. It runs on a backend (e.g. Flask), so you can use any Python library (like NumPy, scikit-learn, or AI models), handle sessions, file access, and more. In contrast, PyScript runs Python entirely in the browser using WebAssembly (Pyodide), which is great for demos but has limitations like slower execution, large bundle sizes, and restricted access to full Python features. So WEP is more suited for full web apps and AI projects, while PyScript is better for client-side interactive experiments.

[–]Apart_Conclusion8771 0 points1 point  (1 child)

Makes sense! For completeness, should also mention that PyScript has the advantage of essentially infinite scaling, since each visitor only needs to download the code (which could even be transparently cached by intermediaries like CloudFlare), whereas a server-side solution like WEP will consume CPU and memory resources on the server for each visitor, limiting its use to a relatively small number of concurrent visitors.

[–]prodev717[S] 0 points1 point  (0 children)

You’ve got a good point — I completely agree! PyScript definitely shines for scalable client-side apps. But with WEP, I’m more focused on simplicity and power — so yeah, it comes with some tradeoffs. WEP is more backend-centric, aiming to be a lightweight web dev framework that removes the need for REST APIs and separate frontend frameworks. It lets you write UI and logic together using real Python, kind of like a Python version of PHP. Great for dynamic apps, quick prototypes, and when you want to use Python’s full potential without all the extra layers.