[names] `__builtin__` is the Python 2 module name; IPython's `run` should be `%run`
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- jupyter-notebook, python
- Domain
- content, documentation
Research direction
The file to edit is lectures/names.md. Look at line 336 to change __builtin__ to builtins and line 229 to change run to %run. Verify the changes by checking the context around those lines. After editing, you can run a quick test by viewing the markdown to ensure the corrections are in place.
Written by the indexing model from the issue text.
Description
Two small inaccuracies in lectures/names.md, found during native-editor review of the French edition (see QuantEcon/lecture-python-programming.fr#80, which corrected both in French). Checked at b0b0b56.
__builtin__ is the Python 2 module name. Line 336 says the built-in definitions "are stored in a module called __builtin__". Python 3.0 renamed that module builtins (What's New in Python 3.0), and import __builtin__ raises ModuleNotFoundError on current Python. Suggested: "These definitions are provided by the builtins module."
run vs %run. Line 229 says "When we run a script using IPython's run command", while the cells at lines 245 and 446 use the %run magic. Bare run only works because automagic is on by default (IPython magics); %run matches the code.
Why it is worth doing soon: until the English agrees, a translation sync that touches the adjacent bullet can revert the French builtins correction (it did in 3 of 3 simulations against the current engine). The Chinese and Persian editions carry both as written.
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 31
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
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.
More from QuantEcon/lecture-python-programming
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
QuantEcon/lecture-python-programming#607 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
QuantEcon/lecture-python-programming#622 · 4 comments ·
All issues in QuantEcon/lecture-python-programming
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100