Programming FAQ about "How do I iterate over a sequence in reverse order?" should be more precise about `reversed`

Open
#84,525 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

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.

Description

3.8 (EOL) 3.9 (EOL) docs type-feature
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']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.