python / python/cpython

venv does not work correctly when imported from .zip

Open
#86,700 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.10 3.8 (EOL) 3.9 (EOL) stdlib type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 42534
Nosy @jussienko

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 2020-12-02.10:18:16.166>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'venv does not work correctly when imported from .zip'
updated_at = <Date 2020-12-02.10:18:16.166>
user = 'https://github.com/jussienko'

bugs.python.org fields:

activity = <Date 2020-12-02.10:18:16.166>
actor = 'jussienko'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-12-02.10:18:16.166>
creator = 'jussienko'
dependencies = []
files = []
hgrepos = []
issue_num = 42534
keywords = []
message_count = 1.0
messages = ['382301']
nosy_count = 1.0
nosy_names = ['jussienko']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42534'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

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.

Research direction

The issue provides no file, test, reproduction steps, or entry point. Start by reproducing the failure involving venv when imported from a .zip, then trace the relevant standard-library implementation and add regression coverage. Done means venv behaves correctly in that zip-import scenario and the test passes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.