What should happen if someone runs ./python -m ensurepip in the build environment?

Open
#64,270 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
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start with the ./python -m ensurepip command named in the issue and investigate how ensurepip behaves when invoked from the build environment. The issue does not identify files, tests, or an expected outcome, so first establish the intended behavior and how it should be verified.

Written by the indexing model from the issue text.

Description

topic-ensurepip
BPO 20071
Nosy @ncoghlan, @ned-deily, @bitdancer, @dstufft

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-26.17:25:26.090>
labels = []
title = 'What should happen if someone runs ./python -m ensurepip in the build environment?'
updated_at = <Date 2014-09-08.11:51:44.568>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2014-09-08.11:51:44.568>
actor = 'ncoghlan'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2013-12-26.17:25:26.090>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 20071
keywords = []
message_count = 3.0
messages = ['206948', '226573', '226574']
nosy_count = 4.0
nosy_names = ['ncoghlan', 'ned.deily', 'r.david.murray', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue20071'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

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.