Repository navigation
Raise the build stack to the shared baseline and drop --upgrade from install lines - #663
Conversation
…install lines environment.yml takes quantecon-book-theme 0.22.2 and sphinx-exercise 1.2.2, the newest releases, which the QuantEcon lecture monorepo's one environment pins (QuantEcon/lectures#70). Five install lines in pandas, pandas_panel, polars and scipy drop --upgrade: in a build every lecture shares one environment, so an --upgrade line replaces the pinned version for every lecture executed after it. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL
There was a problem hiding this comment.
🔵 Needs a closer look
This change alters dependency versions and notebook installation behavior in ways that can affect executed lecture outputs and site rendering, so it requires a fresh full Jupyter Book build/execution and rendering/Colab spot-check before it’s safe to approve.
No open issues 🎉
What changed in this PR
Aligns this lecture series’ build environment with the shared QuantEcon baseline and adjusts notebook-local install cells to avoid unintended environment-wide upgrades during sequential execution.
Changes:
- Update pinned build-stack dependencies in
environment.yml(quantecon-book-theme 0.22.0 → 0.22.2, sphinx-exercise 1.2.1 → 1.2.2). - Remove
--upgradefrom selected lecturepip installcells to prevent overwriting already-installed/pinned packages during full builds.
| File | Description |
|---|---|
| lectures/scipy.md | Removes --upgrade from the lecture’s pip install quantecon cell to avoid upgrading an existing environment install during builds. |
| lectures/polars.md | Removes --upgrade from the pip install polars yfinance cell to prevent overriding preinstalled versions when present. |
| lectures/pandas.md | Drops --upgrade from pip install cells for wbgapi and yfinance to avoid mid-build upgrades that can affect later lectures. |
| lectures/pandas_panel.md | Removes --upgrade from the pip install seaborn cell to preserve the environment-provided seaborn version during execution builds. |
| environment.yml | Bumps pinned documentation/theme dependencies to match the shared baseline (quantecon-book-theme 0.22.2 and sphinx-exercise 1.2.2). |
Review effort: Balanced
Copilot was unable to complete this review at the selected tier due to model policy or plan restrictions.
|
Full site validation: no new warning, no regression.
|
✅ Translation sync completed (zh-cn)Target repo: QuantEcon/lecture-python-programming.zh-cn
|
✅ Translation sync completed (fa)Target repo: QuantEcon/lecture-python-programming.fa
|
✅ Translation sync completed (fr)Target repo: QuantEcon/lecture-python-programming.fr
|
What
The second of six pull requests, one per series, that bring the lecture series to one up-to-date baseline: the environment the QuantEcon lecture monorepo's sites are to build in, pinned in QuantEcon/lectures#70 (
_base/environment-update.yml). Intro's is QuantEcon/lecture-python-intro#872.environment.ymlpandas,pandas_panel,polars,scipy--upgrade:wbgapi,yfinance(twice),seaborn,polarsandquanteconThe GPU workflows already pin
jax[cuda13]==0.11.0, as the monorepo's list does, and the execution workflows install the build stack unpinned, so they take the newest; neither changes.Why the install lines change
In a build every lecture runs in one environment, so an
--upgradeline replaces the version the environment pins for every lecture executed after it. Without--upgradethe line installs the package where it is missing and leaves it alone where it is there. In this series' own buildseaborncomes from Anaconda 2026.07 (0.13.2, also the newest release); the others are not in Anaconda, so the line still installs the newest.For the reviewer: a reader running these notebooks on Colab now gets Colab's preinstalled
yfinance,polars,seabornandquanteconwhere it has them, instead of the newest.Validation
By the owner's rule for any software upgrade on a series, this merges only after a full validation of the site: a fresh build with every lecture executed, compared with one of main for new warnings (DeprecationWarning, FutureWarning, Sphinx), for changed cell outputs and for rendering regressions page by page, plus the Colab path. The evidence follows in a comment.
🤖 Generated with Claude Code
https://claude.ai/code/session_01WT8bMacV9Lmy1VLUc6XJoL