albertjan

4 ms·

1. 1.▲
   by albertjan 9y ago

   What @meredydd means is, leaving the compiler written in javascript but emitting wasm, so compiling python into wasm with javascript. Too many compilers! :P
2. 2.▲
   by albertjan 9y ago

   We're back up! :)
3. 3.▲
   by albertjan 9y ago

   Oh nooo, I'll try and track down the person that has the creds to fix this :) ...
4. 4.▲
   by albertjan 9y ago

   Thanks for this succinct explanation! I've opened an issue on the skulpt repo. https://github.com/skulpt/skulpt/issues/731
5. 5.▲
   by albertjan 9y ago

   Skulpt strings are javascript strings internally, wether or not you add u in front of a string doesn't actually change it's internal representation. We always strive to be as close to cpython as we can, but in this instance we cho
6. 6.▲
   by albertjan 9y ago

   We are working on python3 support and skulpt does have a python3 mode which emulates the biggest differences between py2 and py3. (like from __future__ import). But it doesn't understand any of the new syntax added by python3 yet.
7. 7.▲
   by albertjan 9y ago

   (Contributor to skulpt and pypy.js here) 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