frozen modules are not regenerated on bytecode magic change when cross building
Open
Nobody has claimed this yet.
3.11
build
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 46271 |
|---|---|
| Nosy | @gvanrossum, @tiran, @moreati |
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 2022-01-05.18:27:14.734>
labels = ['type-bug', 'build', '3.11']
title = 'frozen modules are not regenerated on bytecode magic change when cross building'
updated_at = <Date 2022-01-05.18:27:14.734>
user = 'https://github.com/tiran'
bugs.python.org fields:
activity = <Date 2022-01-05.18:27:14.734>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Cross-Build']
creation = <Date 2022-01-05.18:27:14.734>
creator = 'christian.heimes'
dependencies = []
files = []
hgrepos = []
issue_num = 46271
keywords = []
message_count = 1.0
messages = ['409794']
nosy_count = 3.0
nosy_names = ['gvanrossum', 'christian.heimes', 'Alex.Willmer']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46271'
versions = ['Python 3.11']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported failure while cross-building CPython and changing the bytecode magic value; the payload does not identify a source file or test. Trace the frozen-module build steps and determine why regeneration is skipped, then add or update coverage so frozen modules are regenerated when the magic changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100