file iterator "deemed broken"; can resume after StopIteration
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start by reading the linked BPO issue 23455 and the existing Python documentation for file iterators and StopIteration. No source file or test is named in this issue; done would mean documenting whether iteration can resume after StopIteration and addressing the reported behavior clearly.
Written by the indexing model from the issue text.
Description
| BPO | 23455 |
|---|---|
| Nosy | @pitrou |
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 2015-02-12.18:48:54.422>
labels = ['type-bug', 'docs']
title = 'file iterator "deemed broken"; can resume after StopIteration'
updated_at = <Date 2015-07-21.07:29:07.686>
user = 'https://bugs.python.org/dalke'
bugs.python.org fields:
activity = <Date 2015-07-21.07:29:07.686>
actor = 'ethan.furman'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-02-12.18:48:54.422>
creator = 'dalke'
dependencies = []
files = []
hgrepos = []
issue_num = 23455
keywords = []
message_count = 1.0
messages = ['235850']
nosy_count = 3.0
nosy_names = ['dalke', 'pitrou', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23455'
versions = ['Python 3.5']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PolicyEngine/policyengine-us#9559 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
from:qa priority:P2 reliability tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spec-kitty/spec-kitty#4874 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100