Three small errors found in the French review: getting_started (debugger buttons), python_oop (spend, JAVA)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, python
- Domain
- documentation
Research direction
Edit the three spots named in the issue: lectures/getting_started.md around line 394 (remove the repeated “buttons on the” phrase), and lectures/python_oop.md around line 68 (Java, not JAVA) and lines 205 and 226 (spend prints a message; fix the Insufficent typo). Apply the suggested wording, then check the surrounding lecture text still reads correctly.
Written by the indexing model from the issue text.
Description
Found while reviewing the French edition. Each is a small fix to the English, so that every edition gets it.
lectures/getting_started.md, line 394: "You can then step through the code line by line using the buttons on the "Next" button on the CALLSTACK toolbar (located in the right hand window)." The phrase repeats itself. Suggested: "You can then step through the code line by line using the "Next" button on the CALLSTACK toolbar (located in the right-hand window)." Raised on QuantEcon/lecture-python-programming.fr#85.lectures/python_oop.md, line 205: "spend(x)either decreases wealth byxor returns an error if insufficient funds exist". Both versions ofspendin the lecture print a message instead, so suggested: "…or prints a message if insufficient funds exist". The class version (line 226) also misspells it:"Insufficent funds".lectures/python_oop.md, line 68: "JAVA and Ruby are relatively pure OOP." should read "Java".
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 33
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 90/100
QuantEcon/lecture-python-programming#634 ·
Maintainers usually reply within 1 day
-
Prose typos in functions, oop_intro and python_oop (found via French edition review)Possibly taken @SwetaKumari7 claimed this 12 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
QuantEcon/lecture-python-programming#633 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
QuantEcon/lecture-python-programming#608 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
QuantEcon/lecture-python-programming#607 · 1 comment ·
Maintainers usually reply within 1 day
-
[numpy] Duplicated {index} directive under Matrix MultiplicationPossibly taken @mmcky claimed this 13 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
QuantEcon/lecture-python-programming#600 ·
Maintainers usually reply within 1 day
All issues in QuantEcon/lecture-python-programming
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
developmentseed/deck.gl-raster#693 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
dependencies security
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
dev experience
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cuttle-cards/cuttle#1413 ·
Maintainers usually reply within 1 day
-
macOS
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
beyondcode/herd-community#1761 ·