Use $HOSTPYTHON when determining candidate interpreter for $PYTHON_FOR_BUILD.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start by reading the attached Python-hg-723e0a7c4914-fix-PYTHON_FOR_BUILD-detection-v3.patch, then compare it with the earlier patch versions. Verify the candidate interpreter selection uses $HOSTPYTHON when determining $PYTHON_FOR_BUILD, and validate the behavior for the cross-build cases described by the issue.
Written by the indexing model from the issue text.
Description
| BPO | 22100 |
|---|---|
| Nosy | @doko42, @pmp-p, @vadmium, @yan12125 |
| 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 2014-07-29.15:34:01.943>
labels = ['type-feature', 'build']
title = 'Use $HOSTPYTHON when determining candidate interpreter for $PYTHON_FOR_BUILD.'
updated_at = <Date 2021-02-28.09:47:59.482>
user = 'https://bugs.python.org/shiz'
bugs.python.org fields:
activity = <Date 2021-02-28.09:47:59.482>
actor = 'pmpp'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Cross-Build']
creation = <Date 2014-07-29.15:34:01.943>
creator = 'shiz'
dependencies = []
files = ['36150', '36181', '36247']
hgrepos = []
issue_num = 22100
keywords = ['patch']
message_count = 4.0
messages = ['224230', '224422', '224701', '255395']
nosy_count = 6.0
nosy_names = ['doko', 'rpetrov', 'pmpp', 'martin.panter', 'shiz', 'yan12125']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue22100'
versions = ['Python 3.4', 'Python 3.5']
- 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
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
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