py to pyc location mapping with sys.pycache_prefix isn't 1-to-1 on Windows

Open
#90,998 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

No source file or test is identified. Begin by locating the implementation and tests for sys.pycache_prefix and Windows py-to-pyc path mapping, then reproduce the non-1-to-1 behavior. Done means the mapping behaves correctly on Windows with sys.pycache_prefix and the regression is covered by a test.

Written by the indexing model from the issue text.

Description

3.11 3.12 OS-windows stdlib type-bug
BPO 46842
Nosy @pfmoore, @tjguk, @zware, @zooba

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-02-24.03:41:44.728>
labels = ['type-bug', '3.8', '3.9', '3.10', '3.11', 'library', 'OS-windows']
title = "py to pyc location mapping with sys.pycache_prefix isn't 1-to-1 on Windows"
updated_at = <Date 2022-02-24.03:41:44.728>
user = 'https://bugs.python.org/benrg'

bugs.python.org fields:

activity = <Date 2022-02-24.03:41:44.728>
actor = 'benrg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2022-02-24.03:41:44.728>
creator = 'benrg'
dependencies = []
files = []
hgrepos = []
issue_num = 46842
keywords = []
message_count = 1.0
messages = ['413878']
nosy_count = 5.0
nosy_names = ['paul.moore', 'tim.golden', 'benrg', 'zach.ware', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46842'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10', '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.