cross: wrong interpreter returned when no python available
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
build
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44062 |
|---|---|
| Nosy | @moreati, @vfazio |
| PRs |
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 2021-05-06.18:23:43.293>
labels = ['build', '3.9', '3.10', '3.11']
title = 'cross: wrong interpreter returned when no python available'
updated_at = <Date 2021-05-06.19:06:58.698>
user = 'https://github.com/vfazio'
bugs.python.org fields:
activity = <Date 2021-05-06.19:06:58.698>
actor = 'vfazio'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Cross-Build']
creation = <Date 2021-05-06.18:23:43.293>
creator = 'vfazio'
dependencies = []
files = []
hgrepos = []
issue_num = 44062
keywords = ['patch']
message_count = 1.0
messages = ['393125']
nosy_count = 2.0
nosy_names = ['Alex.Willmer', 'vfazio']
pr_nums = ['25951']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue44062'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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.
Research direction
Read the original BPO issue 44062 and inspect linked pull request #25951 first, since the issue is marked for patch review and already has proposed work. Confirm the wrong-interpreter behavior in the cross-build context and use the existing issue and pull request discussion to determine the expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100