EDIT: I just realized this can mean two things:
1. Compiling python source code to Web-assembly.
2. Compiling the python interpreter/compiler to Web-assembly.
EDIT: I just realized this can mean two things:
1. Compiling python source code to Web-assembly.
2. Compiling the python interpreter/compiler to Web-assembly.
That is a difficult question to ask and I think the original developer of pypy.js Ryan Kelly is most suited to answer it. There are some people that have tried feeding the asm.js from pypy.js to the asm.js -> wasm compiler.
Which with a lot of fiddling may work for the non-jitted version. But if you want all the pypy speed you'll want to jit wasm to the browser.
I would love to know if you can do synchronous calls in wasm.
The runtime can be remarkably small (Skulpt is 228kb minified and gzipped, including the standard library), so I think it's a feasible target. (Pypy.js is, of course, enormous!)
WASM ships in every evergreen browser today: http://caniuse.com/#feat=wasm
Only significant browser missing it is IE; only Edge has support.