venv fails when called from within long path on Windows

Open
#88,733 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no source file, test, or reproducible path. Start by reproducing the venv failure from a sufficiently long Windows path, then trace the venv command's Windows path handling; done means venv completes successfully in that location and the regression is covered by an appropriate test.

Written by the indexing model from the issue text.

Description

OS-windows topic-venv
BPO 44567
Nosy @pfmoore, @tjguk, @zware, @eryksun, @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 2021-07-05.15:51:01.619>
labels = ['OS-windows', '3.11']
title = 'venv fails when called from within long path on Windows'
updated_at = <Date 2021-07-05.18:08:39.719>
user = 'https://bugs.python.org/schwaerz'

bugs.python.org fields:

activity = <Date 2021-07-05.18:08:39.719>
actor = 'steve.dower'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2021-07-05.15:51:01.619>
creator = 'schwaerz'
dependencies = []
files = []
hgrepos = []
issue_num = 44567
keywords = []
message_count = 5.0
messages = ['397000', '397010', '397011', '397014', '397015']
nosy_count = 6.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'schwaerz']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue44567'
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.