"make install" will not install pip if already present in user site-packages

Open
#68,606 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system

Research direction

Start by reproducing the behavior of "make install" when pip is already present in user site-packages, then trace the build and installation path involved. Done means that make install installs pip in the intended location despite the existing user-site copy, with coverage for the reported case.

Written by the indexing model from the issue text.

Description

build topic-ensurepip type-bug
BPO 24418
Nosy @ncoghlan, @pitrou, @ned-deily, @asmeurer, @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 2015-06-09.18:01:53.608>
labels = ['type-bug', 'build']
title = '"make install" will not install pip if already present in user site-packages'
updated_at = <Date 2015-06-09.22:32:06.942>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2015-06-09.22:32:06.942>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2015-06-09.18:01:53.608>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 24418
keywords = []
message_count = 3.0
messages = ['245078', '245079', '245081']
nosy_count = 5.0
nosy_names = ['ncoghlan', 'pitrou', 'ned.deily', 'Aaron.Meurer', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24418'
versions = ['Python 2.7', 'Python 3.4', '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.