Don't prevent dict optimization by coupling with OrderedDict

Open
#76,135 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reviewing the historical context in BPO 31954 and the two referenced pull requests, python/cpython#4292 and #4901. The issue mentions no files or tests, so determine the affected interpreter-core entry points before assessing the proposed change. Done means dict optimization is no longer coupled to OrderedDict without regressing the relevant behavior.

Written by the indexing model from the issue text.

Description

3.13 interpreter-core performance type-feature
BPO 31954
Nosy @tim-one, @rhettinger, @methane, @ericsnowcurrently, @serhiy-storchaka
PRs
  • python/cpython#4292
  • python/cpython#4901
    		•

    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 2017-11-06.09:38:00.961>
labels = ['interpreter-core', 'type-feature', '3.8']
title = "Don't prevent dict optimization by coupling with OrderedDict"
updated_at = <Date 2019-04-15.23:11:52.703>
user = 'https://github.com/serhiy-storchaka'

    bugs.python.org fields:

    activity = <Date 2019-04-15.23:11:52.703>
actor = 'methane'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2017-11-06.09:38:00.961>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 31954
keywords = ['patch']
message_count = 15.0
messages = ['305623', '305626', '305715', '305721', '305722', '308459', '308460', '308462', '308465', '308473', '308635', '340183', '340185', '340289', '340306']
nosy_count = 5.0
nosy_names = ['tim.peters', 'rhettinger', 'methane', 'eric.snow', 'serhiy.storchaka']
pr_nums = ['4292', '4901']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31954'
versions = ['Python 3.8']

    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.