docs: summary page - generator vs iterator vs iterable

Open
#62,087 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

No documentation file, test, or entry point is named. Start by locating the summary page referenced in the title and review its existing treatment of generators, iterators, and iterables. Done means the page clearly distinguishes these concepts; confirm the documentation build if the project identifies a relevant check.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) docs type-feature
BPO 17887
Nosy @terryjreedy, @ezio-melotti

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 2013-05-01.06:34:47.938>
labels = ['type-feature', '3.8', '3.9', '3.10', 'docs']
title = 'docs: summary page - generator vs iterator vs iterable'
updated_at = <Date 2020-11-17.22:11:03.014>
user = 'https://bugs.python.org/techtonik'

bugs.python.org fields:

activity = <Date 2020-11-17.22:11:03.014>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2013-05-01.06:34:47.938>
creator = 'techtonik'
dependencies = []
files = []
hgrepos = []
issue_num = 17887
keywords = []
message_count = 3.0
messages = ['188203', '188334', '188336']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'techtonik', 'ezio.melotti', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17887'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

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.