Language reference is ambiguous regarding next() method lookup

Open
#49,989 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the language reference section covering next() method lookup and the linked PR gh-145067. Clarify the wording so the lookup behavior is unambiguous, then verify the documentation accurately describes the existing behavior.

Written by the indexing model from the issue text.

Description

3.13 3.14 3.15 docs type-bug
BPO 5739
Nosy @birkenfeld, @terryjreedy, @ncoghlan

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 2009-04-12.00:58:26.396>
labels = ['type-bug', 'docs']
title = 'Language reference is ambiguous regarding next() method lookup'
updated_at = <Date 2019-03-15.22:55:14.374>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2019-03-15.22:55:14.374>
actor = 'BreamoreBoy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2009-04-12.00:58:26.396>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 5739
keywords = []
message_count = 5.0
messages = ['85883', '86104', '86113', '236179', '236187']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'terry.reedy', 'ncoghlan']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue5739'
versions = []

Linked PRs
  • gh-145067
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.