QuantEcon / QuantEcon/lecture-python.myst
MAINT: tidy up orphaned _static/lecture_specific/optgrowth_fast/ (and related optgrowth-series) files
@Chihiro2000GitHub is already working on this.
Since Aug 13, 2026.
- Dominant language
- TeX
- Stars
- 123
- Forks
- 57
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 11
Description
Background
lectures/_static/lecture_specific/optgrowth_fast/ contains two code snippets (ogm.py, ogm_crra.py)
that were :load:-ed by the old lecture optgrowth_fast.md ("Optimal Growth II: Accelerating the Code
with Numba").
That lecture was deleted in #679 (merged 2025-11-08), which refactored the optimal growth series into
the cake eating series (now the os_* lectures) with inline NamedTuple models. The refactor inlined
or removed the other external code files it used, but this folder was left behind.
Current state
- No lecture references
optgrowth_fast/: there are no:load:directives or other references to
ogm.py/ogm_crra.pyanywhere in the repo, andOptimalGrowthModelappears nowhere outside these
two files. (The only lecture still loading a static.pyismarkov_perf.) - Further evidence the files are never executed:
ogm_crra.pydefinesu_prime_inv(c)withoutself
while its body referencesself.γ, which would fail on any call. - Two other leftovers from the same refactor also appear unreferenced:
_static/lecture_specific/optgrowth/(3ndp.pdf,solution_og_ex2.png)_static/lecture_specific/coleman_policy_iter/(solve_time_iter.py)
- Two open PRs from the QuantEcon/meta#299 RNG migration touch these files: #962 (
ogm.py) and
#963 (ogm_crra.py). Both are blocked on a review question about changing the constructor
signature — which becomes moot if the files are removed.
Proposed tidy-up
- Confirm no external consumers (e.g. other lecture repos fetching these files by raw URL)
- Delete
lectures/_static/lecture_specific/optgrowth_fast/ - Delete (or confirm still wanted)
_static/lecture_specific/optgrowth/and
_static/lecture_specific/coleman_policy_iter/ - Close or repurpose #962 and #963 accordingly
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.