Skip to content

Backport PEP 3114 (__next__) #46589

Description

@brettcannon
BPO 2336
Nosy @brettcannon, @rhettinger, @benjaminp

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 = <Date 2008-07-31.01:53:08.476>
created_at = <Date 2008-03-17.17:49:20.517>
labels = ['type-bug']
title = 'Backport PEP 3114 (__next__)'
updated_at = <Date 2008-07-31.01:53:08.475>
user = 'https://github.com/brettcannon'

bugs.python.org fields:

activity = <Date 2008-07-31.01:53:08.475>
actor = 'benjamin.peterson'
assignee = 'none'
closed = True
closed_date = <Date 2008-07-31.01:53:08.476>
closer = 'benjamin.peterson'
components = []
creation = <Date 2008-03-17.17:49:20.517>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 2336
keywords = ['26backport']
message_count = 3.0
messages = ['63694', '63701', '70456']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'rhettinger', 'benjamin.peterson']
pr_nums = []
priority = 'critical'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2336'
versions = ['Python 2.6']

Activity

  1. brettcannon commented on Mar 17, 2008

    @brettcannon
    MemberAuthor

    PEP-3114 needs to be backported. Most likely the best approach is to
    backport the next() built-in but to have it call next() on the iterator
    instead of __next__(). That should hopefully minimize breakage while
    allowing for moving over to the new built-in.

  2. rhettinger commented on Mar 17, 2008

    @rhettinger
    Contributor

    I don't think this should be backported. It leaves Py2.6 with a
    confused mess of protocols. The 2-to-3 transformation is simple.
    Backporting doesn't add value.

  3. benjaminp commented on Jul 31, 2008

    @benjaminp
    Contributor

    This has been done.

  4. transferred this issue fromon Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type-bugAn unexpected behavior, bug, or error

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions