frozen modules are not regenerated on bytecode magic change when cross building

Open
#90,429 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system

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.

Description

3.11 build type-bug
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']

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.