Following the move to Python 3.14 (see #68), two installation screencasts show Python 3.13 on camera and need re-recording.
python_installation_execution/pixi_and_conda_forge
The slides walk through creating an environment "Using Python 3.13" with pixi add python=3.13. The python-kaleido + pixi run plotly_get_chrome flow it shows is still current for kaleido 1.x; only the Python version is stale.
python_installation_execution/pixi_modifying_environments
The shown pyproject.toml pins python = ">=3.13" and numpy = ">=2.2.3", and the deck displays captured pixi list terminal output at python 3.13.2. Because the captured output and the narration are locked to the recording, this one cannot be spot-edited and needs a full re-record on the new stack.
Both are minor (installation walk-throughs), but they should match the Python 3.14 environments the courses now ship.
Following the move to Python 3.14 (see #68), two installation screencasts show Python 3.13 on camera and need re-recording.
python_installation_execution/pixi_and_conda_forgeThe slides walk through creating an environment "Using Python 3.13" with
pixi add python=3.13. Thepython-kaleido+pixi run plotly_get_chromeflow it shows is still current for kaleido 1.x; only the Python version is stale.python_installation_execution/pixi_modifying_environmentsThe shown
pyproject.tomlpinspython = ">=3.13"andnumpy = ">=2.2.3", and the deck displays capturedpixi listterminal output atpython 3.13.2. Because the captured output and the narration are locked to the recording, this one cannot be spot-edited and needs a full re-record on the new stack.Both are minor (installation walk-throughs), but they should match the Python 3.14 environments the courses now ship.