Repository navigation
Hero and docs runtimes take env_set from boarddev (lands with the wasm rebuild) - #62
Conversation
pydevices moved env_get, env_int, env_float, env_bool and env_set from displaydev to boarddev with no re-export (a hard break). The pages run on the vendored wasm with pydevices frozen in, so this lands with the wasm rebuild that freezes the new pydevices, not before.
|
This repo is the source. |
|
generator-idempotency fails here as expected. It regenerates PyDevices.github.io from this branch and diffs the result against PyDevices.github.io main, and the only difference is the four import lines in PyDevices/PyDevices.github.io#17. Merge #17 first (or at the same moment) and this check passes. |
|
The rebuilt runtime landed in PyDevices/PyDevices.github.io#17 (eb5db2b), with that site's generated copy of these four files. Ran in Chromium against it: every hero reaches |
PyDevices/pydevices#131 moves
env_get,env_int,env_float,env_boolandenv_setfrom displaydev to boarddev as a hard break. The hero runtime, the docs runtime,watch.pyandsignal_gen.pynow import them from boarddev.Don't merge this on its own. These pages run the vendored
/vendor/micropython/micropython.wasm (served by PyDevices.github.io), which has pydevices frozen in. Today's wasm has the old boarddev, with noenv_set, so this change would take every hero and docs demo offline. Merge it in the same commit or sitting as the wasm rebuild that freezes #131's pydevices (pin move in micropython-pydevices, rebuild, re-vendor into PyDevices.github.io). Until then the current wasm and the current JS agree with each other and keep working.That rebuild also fixes the examples gallery, which boots this site's wasm. After PyDevices/pydevices-examples#183 merges, the gallery's env-using examples need the new wasm.
Not tested in a browser: there's no wasm with the new pydevices to test against yet. The change is the import line in four files.