python / python/cpython

venv module does not copy the correct python exe

Open
#87,915 20 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

OS-windows stdlib topic-venv
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 43749
Nosy @pfmoore, @vsajip, @tjguk, @zware, @eryksun, @zooba, @miss-islington, @NiklasRosenstein, @inorton, @mitchhentges
PRs
  • python/cpython#25216
  • python/cpython#30033
  • python/cpython#30034
  • 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-04-06.13:27:05.454>
    labels = ['3.10', 'library', '3.9', 'OS-windows', '3.11']
    title = 'venv module does not copy the correct python exe'
    updated_at = <Date 2021-12-11.03:21:25.207>
    user = 'https://github.com/inorton'
    

    bugs.python.org fields:

    activity = <Date 2021-12-11.03:21:25.207>
    actor = 'eryksun'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)', 'Windows']
    creation = <Date 2021-04-06.13:27:05.454>
    creator = 'Ian Norton'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 43749
    keywords = ['patch']
    message_count = 13.0
    messages = ['390329', '390330', '396286', '396287', '408224', '408228', '408229', '408231', '408233', '408234', '408247', '408279', '408289']
    nosy_count = 10.0
    nosy_names = ['paul.moore', 'vinay.sajip', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower', 'miss-islington', 'n_rosenstein', 'Ian Norton', 'mitchhentges']
    pr_nums = ['25216', '30033', '30034']
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue43749'
    versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
    

    Linked PRs
    • gh-129495

    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

    Start by reviewing the referenced BPO issue 43749 and the listed PRs 25216, 30033, 30034, plus linked PR gh-129495, since the issue body names no files or tests. Use those discussions to identify the Windows venv entry point and the expected executable-copy behavior; done means the correct Python executable is copied.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    devtools, operating-systems
    Issue type
    Bug
    Difficulty
    3/5
    Estimated time
    1-2 days
    Activity status
    Stale
    Clarity
    Needs clarification
    Newbie friendliness
    20/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.