Lazy execution of module bytecode

Open
#77,305 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the original bugs.python.org issue 33124 and the referenced pull request python/cpython#6194. The payload names no files, tests, entry points, or acceptance criteria, so the intended lazy-execution behavior and definition of done must be established before implementation.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 33124
Nosy @warsaw, @brettcannon, @nascheme, @serhiy-storchaka, @MojoVampire
PRs
  • python/cpython#6194
    		•

    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-03-22.22:17:11.808>
labels = ['interpreter-core', 'type-feature']
title = 'Lazy execution of module bytecode'
updated_at = <Date 2018-03-28.15:18:32.954>
user = 'https://github.com/nascheme'

    bugs.python.org fields:

    activity = <Date 2018-03-28.15:18:32.954>
actor = 'josh.r'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-03-22.22:17:11.808>
creator = 'nascheme'
dependencies = []
files = []
hgrepos = []
issue_num = 33124
keywords = ['patch']
message_count = 3.0
messages = ['314294', '314505', '314606']
nosy_count = 5.0
nosy_names = ['barry', 'brett.cannon', 'nascheme', 'serhiy.storchaka', 'josh.r']
pr_nums = ['6194']
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33124'
versions = []

    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.