ensurepip does not honour the value of $(prefix)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by reviewing the linked ensurepip_prefix.diff and the ensurepip implementation in CPython, then inspect PRs 17634, 19068, and gh-135488 for the current state. Done means ensurepip respects the configured $(prefix) during cross-builds, with the relevant regression coverage updated or added.
Written by the indexing model from the issue text.
Description
| BPO | 31046 |
|---|---|
| Nosy | @ncoghlan, @mcepl, @vadmium, @dstufft, @moreati, @ZackerySpytz |
| PRs | |
| Files |
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 2017-07-26.16:39:28.627>
labels = ['type-bug', '3.9', 'build']
title = 'ensurepip does not honour the value of $(prefix)'
updated_at = <Date 2020-03-19.10:08:27.658>
user = 'https://github.com/xdegaye'
bugs.python.org fields:
activity = <Date 2020-03-19.10:08:27.658>
actor = 'mcepl'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Cross-Build']
creation = <Date 2017-07-26.16:39:28.627>
creator = 'xdegaye'
dependencies = []
files = ['47041']
hgrepos = []
issue_num = 31046
keywords = ['patch']
message_count = 3.0
messages = ['299252', '299290', '330805']
nosy_count = 6.0
nosy_names = ['ncoghlan', 'mcepl', 'martin.panter', 'dstufft', 'Alex.Willmer', 'ZackerySpytz']
pr_nums = ['17634', '19068']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue31046'
versions = ['Python 3.9']
Linked PRs
- gh-135488
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100