Programming FAQ about "How do I iterate over a sequence in reverse order?" should be more precise about `reversed`
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
docs
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40345 |
|---|---|
| Nosy | @Dominik1123 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2020-04-20.21:38:25.709>
labels = ['type-feature', '3.8', '3.9', 'docs']
title = 'Programming FAQ about "How do I iterate over a sequence in reverse order?" should be more precise about `reversed`'
updated_at = <Date 2020-04-20.21:38:25.709>
user = 'https://github.com/Dominik1123'
bugs.python.org fields:
activity = <Date 2020-04-20.21:38:25.709>
actor = 'Dominik V.'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2020-04-20.21:38:25.709>
creator = 'Dominik V.'
dependencies = []
files = []
hgrepos = []
issue_num = 40345
keywords = []
message_count = 1.0
messages = ['366889']
nosy_count = 2.0
nosy_names = ['docs@python', 'Dominik V.']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40345'
versions = ['Python 3.8', 'Python 3.9']
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 locating the Programming FAQ entry titled "How do I iterate over a sequence in reverse order?" and read its current explanation of reversed. Clarify the wording so it precisely describes reversed, then verify that the revised FAQ is accurate and consistent with the surrounding documentation.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100