QuantEcon / QuantEcon/lecture-python-programming.fr
Review: debugging.md
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 41m
- Merged PRs (30d)
- 3
Description
Part of #40 (Phase 1).
Native-speaker review of debugging.md by @Honaminto.
| French (read this) | lectures/debugging.md |
| English source | lectures/debugging.md |
How to reply. Open a PR editing the French directly — one PR for this lecture, titled e.g. [debugging] Corrections — or leave line comments / suggestion blocks on it. Priorities: meaning errors, wrong technical terms, inconsistent terminology, unnatural French (academic register), anything in code comments that looks wrong. Ignore spacing before : ; ! ?, errors in the English, and the translation: header. A wrong term that recurs belongs on the terminology issue, not here.
Done when a PR by @Honaminto touching this file is merged, or he states here that the lecture needs no change. Either outcome is recorded; nothing is ticked by hand.
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.
Research direction
Start by comparing lectures/debugging.md in the French repository with the English source at the linked files. Review meaning, technical terms, terminology consistency, academic French, and code comments while ignoring the listed spacing and header concerns. Done means a PR touching the French file is merged, or the reviewer states that no changes are needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100