








console.log everywhere












































$ PWDEBUG=1 pytest










docs/developers/ with little notes to write down the thinking on hard things.

docs/developers/ with little notes to write down the thinking on hard things. 





Element and friends (edited)









$ git clone git@github.com:pyscript/pyscript-collective.git
$ cd pyscript-collective
$ poetry install
$ poetry run psc build$ poetry run psc download
$ poetry run pytest













pyscript.css















py-terminal , which implies that print("hello") doesn't show anything by default
2) we include py-terminal but you have to style it yourself
3) we include py-terminal and we give it a default style
Personally, I think that (3) is the best choice, but we can debate of course

























manylinux1_compatible, and manylinux_${GLIBCMAJOR}_${GLIBCMINOR}_${ARCH} could be in fact manylinux_<emscriptenversion> from https://peps.python.org/pep-0600/ (edited)
time function changing from (i32) -> i32 to (i32) -> i64. If a module was built with a version of Emscripten that gives it the former signature and someone tries to link it against a Pyodide built with the latter signature, then it crashes at load time. There is no "MVP" or "backwards compatible" flag, if Emscripten changes its ABI then the modules can't work together.
As far as actual wasm features, we require bigInt and mutableGlobals for everything, but other than that I think none of the other features are used in our wheels. Of course, we could imagine making simd enabled builds of packages like numpy...

time has signature (i32) -> i32 and it actually had signature (i32) -> i64.

time has signature (i32) -> i32 and it actually had signature (i32) -> i64. 
















iframe technique video embedding uses).































