reversed() does not work with weakref.proxy of sequences

Open
#63,558 10 comments 0 reactions 1 assignee View on GitHub

@benjaminp is already working on this.

Since Mar 14, 2014.

Assessment

This issue has not been assessed yet.

Description

stdlib type-bug
BPO 19359
Nosy @rhettinger, @pitrou, @vstinner, @benjaminp, @PCManticore, @iritkatriel
Files
  • reversed_proxy_failure.py: Demonstrates issue
  • reversed_proxy.patch
  • issue19359.patch: Remove trailing whitespace.
  • reversed_list_proxy_test.py: Show that reversed isn't detected on a proxy
    		•

    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 = 'https://github.com/benjaminp'
closed_at = None
created_at = <Date 2013-10-23.07:00:08.425>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'reversed() does not work with weakref.proxy of sequences'
updated_at = <Date 2021-03-14.17:52:30.538>
user = 'https://bugs.python.org/abingham'

    bugs.python.org fields:

    activity = <Date 2021-03-14.17:52:30.538>
actor = 'iritkatriel'
assignee = 'benjamin.peterson'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-10-23.07:00:08.425>
creator = 'abingham'
dependencies = []
files = ['32309', '32322', '34376', '34413']
hgrepos = []
issue_num = 19359
keywords = ['patch']
message_count = 8.0
messages = ['201002', '201069', '213526', '213528', '213529', '213530', '213562', '388678']
nosy_count = 7.0
nosy_names = ['rhettinger', 'pitrou', 'vstinner', 'benjamin.peterson', 'Claudiu.Popa', 'abingham', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue19359'
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.