Add path expansion interpolation in pyvenv.cfg home key

Open
#78,688 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
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start by locating CPython's handling of the pyvenv.cfg home key and review how path values are currently read. The issue names no files, tests, or entry points, so identify the relevant implementation and test locations before defining the expected interpolation behavior. Done means the home key expands paths consistently and the behavior is covered by tests.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 34507
Nosy @chnlior

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 2018-08-26.11:00:21.908>
labels = ['interpreter-core', 'type-feature']
title = 'Add path expansion interpolation in pyvenv.cfg home key'
updated_at = <Date 2018-08-26.11:00:21.908>
user = 'https://github.com/chnlior'

bugs.python.org fields:

activity = <Date 2018-08-26.11:00:21.908>
actor = 'chnlior'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-08-26.11:00:21.908>
creator = 'chnlior'
dependencies = []
files = []
hgrepos = []
issue_num = 34507
keywords = []
message_count = 1.0
messages = ['324116']
nosy_count = 1.0
nosy_names = ['chnlior']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34507'
versions = ['Python 3.6']

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.