Add feature to allow code execution prior to __main__ invocation

Open
#59,008 30 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
compilers

Research direction

Start by reading the linked BPO issue 14803 and its discussion, since no files, tests, or implementation entry points are identified here. Establish the intended execution semantics and acceptance criteria for running code before main invocation before locating the relevant interpreter-core code and tests.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 14803
Nosy @warsaw, @gpshead, @ncoghlan, @pitrou, @kristjanvalur, @nedbat, @asvetlov, @cjerdonek, @ericsnowcurrently, @serhiy-storchaka

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 2012-05-14.07:43:38.982>
labels = ['interpreter-core', 'type-feature']
title = 'Add feature to allow code execution prior to __main__ invocation'
updated_at = <Date 2020-05-12.13:06:24.826>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2020-05-12.13:06:24.826>
actor = 'ionelmc'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-05-14.07:43:38.982>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 14803
keywords = []
message_count = 27.0
messages = ['160597', '160642', '160647', '160657', '160680', '160700', '160702', '160703', '160710', '160713', '166722', '166747', '166752', '166755', '166762', '166763', '166765', '166772', '166779', '166785', '166841', '166843', '167005', '167066', '176889', '176915', '368728']
nosy_count = 14.0
nosy_names = ['barry', 'gregory.p.smith', 'ncoghlan', 'pitrou', 'kristjan.jonsson', 'nedbat', 'Arfrever', 'ionelmc', 'asvetlov', 'chris.jerdonek', 'eric.snow', 'serhiy.storchaka', 'bkabrda', 'bfroehle']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14803'
versions = ['Python 3.4']

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.