Replies: 4 comments
-
|
hi, yes we already can compile the app's Python code to WebAssembly check out |
Beta Was this translation helpful? Give feedback.
-
|
Sounds good. That just leaves tree shaking I guess, similar to what Blazor does (since Microsoft don't want Blazor apps to ship the entire .NET Framework to the user, as it's quite large, it removes bits that aren't used as part of the build) |
Beta Was this translation helpful? Give feedback.
-
|
yup, work is being done on tree shaking check this out https://jott.live/markdown/wasm_binary_size and we are looking into other things to do to |
Beta Was this translation helpful? Give feedback.
-
|
Great suggestions, thanks @Daniel15 !
I think the problem with this is that the problem is not only pre-compiling but also running it for the first time. It takes time. (I may be wrong here though).
There's work being done about that upstream. For instance pyodide-pack is a great example.
This is less about "real use cases" and more about being viable to specific use cases. PyScript is much of an experiment as any project so early in its development. There are specific use cases that will never be good ones for PyScript but there are many use cases where PyScript is a viable option today. If you can elaborate on your use cases it could definitely be interesting for the core team to take into consideration as PyScript matures. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
For production use cases, it'd be useful to:
This could probably make it viable for some real use cases rather than just as an experiment 😄
Beta Was this translation helpful? Give feedback.
All reactions