Frozen modules are looked up using a linear search.

Open
#89,376 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
performance

Research direction

The payload names no files, tests, or entry points. Start by tracing CPython's frozen-module lookup and confirm where the linear search occurs; done means frozen modules are looked up without that linear scan while preserving existing import behavior.

Written by the indexing model from the issue text.

Description

3.12 interpreter-core performance
BPO 45213
Nosy @malemburg, @warsaw, @brettcannon, @rhettinger, @ericsnowcurrently, @zooba, @corona10

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-09-15.17:42:12.775>
labels = ['interpreter-core', '3.11', 'performance']
title = 'Frozen modules are looked up using a linear search.'
updated_at = <Date 2021-09-24.10:59:10.247>
user = 'https://github.com/ericsnowcurrently'

bugs.python.org fields:

activity = <Date 2021-09-24.10:59:10.247>
actor = 'corona10'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-09-15.17:42:12.775>
creator = 'eric.snow'
dependencies = []
files = []
hgrepos = []
issue_num = 45213
keywords = []
message_count = 9.0
messages = ['401863', '401864', '402198', '402232', '402431', '402433', '402447', '402505', '402552']
nosy_count = 7.0
nosy_names = ['lemburg', 'barry', 'brett.cannon', 'rhettinger', 'eric.snow', 'steve.dower', 'corona10']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue45213'
versions = ['Python 3.11']

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.