[need_for_speed.md] Update np.random → Generator API#545
Merged
HumphreyYang merged 2 commits intomainfrom May 5, 2026
Merged
Conversation
HumphreyYang
approved these changes
May 5, 2026
Member
HumphreyYang
left a comment
HumphreyYang
left a comment
There was a problem hiding this comment.
Many thanks @Chihiro2000GitHub, it looks great to me. Merging
Contributor
✅ Translation sync completed (zh-cn)Target repo: QuantEcon/lecture-python-programming.zh-cn
|
Contributor
✅ Translation sync completed (fa)Target repo: QuantEcon/lecture-python-programming.fa
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates
lectures/need_for_speed.mdas part of the NumPy random API migration described in QuantEcon/meta#299.The change is limited to one remaining legacy NumPy random API usage in the vectorized NumPy example ("9.4.2. Vectorization vs pure Python loops").
The
rnggenerator is initialized outside thewith qe.Timer():block, so the timing comparison continues to measure only the vectorized NumPy operation itself.I also checked the rendered lecture with a local build. The relative timing difference between the non-vectorized Python loop and the vectorized NumPy version remains essentially unchanged, so the speed comparison in the lecture is not affected by this update.
@HumphreyYang, I'd be grateful if you could take a look when you have time!