Problem
quantecon/__init__.py has carried the comment "Imports that Should be Deprecated with markov package" above mc_compute_stationary and mc_sample_path (markov/core.py:696,711) across many release cycles — but neither function warns. The deprecation exists only for people reading our source: users get no signal, so eventual removal would feel abrupt, while keeping the aliases forever contradicts the stated intent. Both are thin wrappers over MarkovChain.
Proposed change
Decide, then implement — either branch is small:
A. Deprecate for real: add warnings.warn(..., DeprecationWarning, stacklevel=2) naming the replacement (MarkovChain(P).stationary_distributions / MarkovChain(P).simulate(...)) and a target removal version; changelog entry; pytest.warns test. This matches the module docstrings' direction, and given #865 is deciding shim-removal scheduling, the same release train could carry both notices.
B. Bless them: delete the comment, add both to the documented API, add tests.
Acceptance criteria
From the July 2026 technical-debt audit (AI-assisted; claims verified against 28d4b3b on 2026-07-25).
Problem
quantecon/__init__.pyhas carried the comment "Imports that Should be Deprecated with markov package" abovemc_compute_stationaryandmc_sample_path(markov/core.py:696,711) across many release cycles — but neither function warns. The deprecation exists only for people reading our source: users get no signal, so eventual removal would feel abrupt, while keeping the aliases forever contradicts the stated intent. Both are thin wrappers overMarkovChain.Proposed change
Decide, then implement — either branch is small:
A. Deprecate for real: add
warnings.warn(..., DeprecationWarning, stacklevel=2)naming the replacement (MarkovChain(P).stationary_distributions/MarkovChain(P).simulate(...)) and a target removal version; changelog entry;pytest.warnstest. This matches the module docstrings' direction, and given #865 is deciding shim-removal scheduling, the same release train could carry both notices.B. Bless them: delete the comment, add both to the documented API, add tests.
Acceptance criteria
From the July 2026 technical-debt audit (AI-assisted; claims verified against
28d4b3bon 2026-07-25).