Repository navigation
Prove the notebook scenario end to end from an installed wheel #19
Description
What
Install the built wheel into a desktop host and run the notebook's scenario there: declare a root, redeclare it, share state between a cell and the screen, and type into a TextField.
Why
The maintainer's bar is "usable for real" by the end of November. M2 proves each widget and M3 proves the wheel's contents, but nothing yet proves the pieces work together from an installed package rather than a source checkout.
Host
python-multiplatform's E2E fixture module, thisisthepy/python-multiplatform#26, not sample/: sample/ is maintainer-authored specification and is not turned into test code. The host draws through python-multiplatform-compose's entry point (thisisthepy/python-multiplatform#18). How it receives the wheel (path or version) is agreed once #18 lands.
Done when
The notebook scenario passes in the python-multiplatform E2E module (thisisthepy/python-multiplatform#26) against this package's wheel, with assertions on rendered pixels and state values.
Activity
b-re-w commentedon Oct 3, 2026
Evidence: python-multiplatform
ksp-fixtures/notebook-e2e(#26, merged via #170, develop844cf291; SPEC B-10implementedon desktop). It ran 20 of 20 passed against this package'sdevelopwheel on 2026-10-04 (after python-multiplatform #146 and #168 and this repo's #88). The wheel is unpacked into the host's site-packages, and the tests requirepythonx.compose.__file__to be inside it. Recorded in SPEC via #96. Caveat: no CI workflow runs that module yet, so this is one local run.Done-when met. The notebook scenario (declare, redeclare, shared state, TextField typing, and the practice cells) passes in the python-multiplatform E2E module against this package's wheel, with assertions on rendered pixels and state values. Left over: no CI runs the module yet. That is python-multiplatform's workflow decision (its README: "Which of the two CI wants is CI's decision").