PyZipFile mixes compiled files from different python versions.

Open
#68,982 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start with the PyZipFile implementation and its handling of compiled Python files. The payload names no source file, test, or reproduction steps, so first locate the relevant standard-library entry point and establish how files from different Python versions are selected. Done means PyZipFile no longer mixes incompatible compiled files, with regression coverage for the reported behavior.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 24794
Nosy @bitdancer

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 2015-08-05.09:43:32.645>
labels = ['type-bug']
title = 'PyZipFile mixes compiled files from different python versions.'
updated_at = <Date 2015-08-05.14:47:16.866>
user = 'https://bugs.python.org/AmundHov'

bugs.python.org fields:

activity = <Date 2015-08-05.14:47:16.866>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2015-08-05.09:43:32.645>
creator = 'Amund Hov'
dependencies = []
files = []
hgrepos = []
issue_num = 24794
keywords = []
message_count = 2.0
messages = ['248024', '248041']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'Amund Hov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24794'
versions = []

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.