<whitequark[cis]>
re uart: there are some pretty annoying termios-related issues that pyodide developers promised to fix "tomorrow" so no
<whitequark[cis]>
re benchmark: yeah i've asked about the exception, i think that's a pyodide problem not a glasgow problem
<whitequark[cis]>
re: looking into it: just clone the repo and hack on index.html
<whitequark[cis]>
there is no CI, build steps, or anything else involved
<whitequark[cis]>
also if you'd like you can review #960
<sazzach[m]>
So would the flow for seeing how a change to the glasgow source affects the webassembly site be to build a wheel with the changed code and move it where the wheel is currently?
<whitequark[cis]>
yes, and then empty-cache-plus-hard-reload (or just append ?1 to the URL in micropip.install where 1 is an increasing number)
<whitequark[cis]>
pyodide itself and the other wheels (markupsafe and cobs) are ones that required some customization, but all of this will be in the next pyodide release
<sazzach[m]>
Re 960: sure I'm down to review! (I should have time later tonight)
<sazzach[m]>
RE webassembly glasgow in general: This is really cool! I can see loaning mine to a friend and or coworker and pointing them to the site to try things. Also having it makes the project more accessible.