Make pyvenv style virtual environments easier to configure when embedding Python

Open
#66,409 70 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the linked gh-127974 PR and dependency bpo-22257, which concerns the PEP 432/587 interpreter startup redesign. Done means pyvenv-style virtual environments are easier to configure when embedding Python, with the scope of the linked work resolved.

Written by the indexing model from the issue text.

Description

docs tests topic-venv type-feature
BPO 22213
Nosy @ncoghlan, @pitrou, @vstinner, @methane, @ericsnowcurrently, @zooba, @ndjensen, @LeslieGerman, @M-Kerr, @abrunner73
Dependencies
  • bpo-22257: PEP 432 (PEP 587): Redesign the interpreter startup sequence
  • 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 2014-08-17.11:42:41.318>
    labels = ['type-feature', '3.8']
    title = 'Make pyvenv style virtual environments easier to configure when embedding Python'
    updated_at = <Date 2021-12-08.21:26:34.716>
    user = 'https://bugs.python.org/grahamd'
    

    bugs.python.org fields:

    activity = <Date 2021-12-08.21:26:34.716>
    actor = 'ndjensen'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2014-08-17.11:42:41.318>
    creator = 'grahamd'
    dependencies = ['22257']
    files = []
    hgrepos = []
    issue_num = 22213
    keywords = []
    message_count = 31.0
    messages = ['225434', '225436', '225437', '225739', '225742', '225771', '225774', '225890', '334926', '334948', '335015', '335468', '335470', '335479', '335484', '335648', '335650', '335688', '335692', '335749', '336793', '343636', '352905', '354856', '354857', '354858', '361600', '361869', '362260', '366570', '384496']
    nosy_count = 13.0
    nosy_names = ['ncoghlan', 'pitrou', 'vstinner', 'pyscripter', 'grahamd', 'methane', 'eric.snow', 'steve.dower', 'Henning.von.Bargen', 'ndjensen', 'Leslie', 'M.Kerr', 'abrunner73']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue22213'
    versions = ['Python 3.8']
    

    Linked PRs
    • gh-127974
    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.