Support embedding the standard library in an executable

Open
#70,195 12 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
build-system, compilers

Research direction

The issue names no files, entry points, or tests; begin by reading BPO issue 26007 and its 12-message discussion. Clarify the executable-embedding scope and identify the relevant interpreter-core tests; completion would require agreed behavior and passing tests.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 26007
Nosy @malemburg, @pfmoore

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 2016-01-04.16:13:13.451>
labels = ['interpreter-core', 'type-feature']
title = 'Support embedding the standard library in an executable'
updated_at = <Date 2020-09-11.23:15:20.621>
user = 'https://bugs.python.org/philthompson10'

bugs.python.org fields:

activity = <Date 2020-09-11.23:15:20.621>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-01-04.16:13:13.451>
creator = 'philthompson10'
dependencies = []
files = []
hgrepos = []
issue_num = 26007
keywords = []
message_count = 12.0
messages = ['257464', '257465', '257466', '257469', '257470', '257477', '257480', '257493', '257495', '257496', '257503', '376748']
nosy_count = 3.0
nosy_names = ['lemburg', 'paul.moore', 'philthompson10']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue26007'
versions = ['Python 3.5', 'Python 3.6']

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.