Provide a robust O(1) mechanism to check for infinite iterators
Open
Nobody has claimed this yet.
3.8 (EOL)
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 33939 |
|---|---|
| Nosy | @rhettinger, @ncoghlan, @pitrou, @embray, @serhiy-storchaka, @jdemeyer, @k7hoven, @bbayles |
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 2018-06-22.12:48:14.537>
labels = ['type-feature', '3.8']
title = 'Provide a robust O(1) mechanism to check for infinite iterators'
updated_at = <Date 2018-09-04.01:06:44.169>
user = 'https://github.com/ncoghlan'
bugs.python.org fields:
activity = <Date 2018-09-04.01:06:44.169>
actor = 'koos.zevenhoven'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2018-06-22.12:48:14.537>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 33939
keywords = []
message_count = 19.0
messages = ['320229', '320232', '320234', '320235', '320237', '320239', '320241', '320297', '320323', '320350', '320352', '320554', '320567', '320568', '320580', '320581', '320589', '323666', '324548']
nosy_count = 8.0
nosy_names = ['rhettinger', 'ncoghlan', 'pitrou', 'erik.bray', 'serhiy.storchaka', 'jdemeyer', 'koos.zevenhoven', 'bbayles']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33939'
versions = ['Python 3.8']
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
The issue names no files, tests, or entry points; start by reading the linked BPO issue and its 19-message discussion. The work is not ready to start until the desired O(1) mechanism, implementation location, and verification criteria are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100