venv.EnvBuilder environmental variable hooks

Open
#81,530 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
10/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Review python/cpython#14272 and the linked BPO issue first; the payload names no source files or tests. Confirm whether the proposed environmental-variable hooks remain needed and identify the current venv.EnvBuilder entry point before defining what done looks like.

Written by the indexing model from the issue text.

Description

stdlib topic-venv type-feature
BPO 37349
Nosy @brettcannon, @vsajip, @cdonovick
PRs
  • python/cpython#14272
    		•

    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 2019-06-20.14:42:40.544>
labels = ['type-feature', 'library', '3.9']
title = 'venv.EnvBuilder environmental variable hooks'
updated_at = <Date 2019-06-21.07:30:50.326>
user = 'https://github.com/cdonovick'

    bugs.python.org fields:

    activity = <Date 2019-06-21.07:30:50.326>
actor = 'vinay.sajip'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-20.14:42:40.544>
creator = 'donovick'
dependencies = []
files = []
hgrepos = []
issue_num = 37349
keywords = ['patch']
message_count = 13.0
messages = ['346122', '346124', '346140', '346144', '346147', '346149', '346155', '346160', '346167', '346169', '346170', '346173', '346187']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'vinay.sajip', 'donovick']
pr_nums = ['14272']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37349'
versions = ['Python 3.9']

    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.