dict subclassing is slow

Open
#89,084 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
api, performance

Research direction

Start with the migrated BPO issue 44921 and its C API and performance labels. The payload names no source file, test, or entry point, so first identify the dict-subclassing path and a way to measure its performance. Done means the reported slowness is addressed and the relevant performance behavior is verified.

Written by the indexing model from the issue text.

Description

3.12 interpreter-core performance
BPO 44921
Nosy @gvanrossum, @willingc, @Marco-Sulla, @jdevries3133

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 2021-08-15.20:10:26.716>
labels = ['expert-C-API', '3.9', 'performance']
title = 'dict subclassing is slow'
updated_at = <Date 2021-08-19.16:21:29.873>
user = 'https://github.com/Marco-Sulla'

bugs.python.org fields:

activity = <Date 2021-08-19.16:21:29.873>
actor = 'Marco Sulla'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['C API']
creation = <Date 2021-08-15.20:10:26.716>
creator = 'Marco Sulla'
dependencies = []
files = []
hgrepos = []
issue_num = 44921
keywords = []
message_count = 6.0
messages = ['399625', '399632', '399790', '399791', '399797', '399922']
nosy_count = 5.0
nosy_names = ['gvanrossum', 'willingc', 'Kevin Shweh', 'Marco Sulla', 'jack__d']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue44921'
versions = ['Python 3.9']

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.