`true` and `false` defined multiple times
Open
Nobody has claimed this yet.
- Dominant language
- reStructuredText
- Stars
- 497
- Forks
- 41
- Avg merge
- 3h 52m
- Merged PRs (30d)
- 4
Description
The tokens true and false are separately defined twice, first in §2.4.7 (as Boolean literals) and again in §2.6.1 (as strict keywords).
Contributor guide
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 the definitions of true and false in §2.4.7 and §2.6.1. Determine which section should own the normative definition, update the duplicate wording or cross-reference, and build or validate the FLS documentation to confirm the tokens are defined only once.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100