Add a "target" parameter to runpy.run_path and runpy.run_module

Open
#64,181 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the runpy.run_path and runpy.run_module entry points and the dependent BPO-19700 work on the PEP 451 update. The issue names no files, tests, or target semantics, so first establish the intended API behavior with the listed nosy contributors. Done requires an agreed implementation, coverage for both entry points, and corresponding documentation.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 19982
Nosy @brettcannon, @ncoghlan, @ericsnowcurrently, @CuriousLearner, @nanjekyejoannah
Dependencies
  • bpo-19700: Update runpy for PEP 451
  • 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 2013-12-14.13:22:03.091>
    labels = ['type-feature', '3.8']
    title = 'Add a "target" parameter to runpy.run_path and runpy.run_module'
    updated_at = <Date 2019-08-06.17:38:32.963>
    user = 'https://github.com/ncoghlan'
    

    bugs.python.org fields:

    activity = <Date 2019-08-06.17:38:32.963>
    actor = 'nanjekyejoannah'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2013-12-14.13:22:03.091>
    creator = 'ncoghlan'
    dependencies = ['19700']
    files = []
    hgrepos = []
    issue_num = 19982
    keywords = []
    message_count = 5.0
    messages = ['206181', '206430', '305671', '305719', '349121']
    nosy_count = 6.0
    nosy_names = ['brett.cannon', 'ncoghlan', 'eric.snow', 'piotr.dobrogost', 'CuriousLearner', 'nanjekyejoannah']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue19982'
    versions = ['Python 3.8']
    

    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.