AC_COMPILE_IFELSE doesn't work in all cases
Open
Nobody has claimed this yet.
3.9 (EOL)
build
interpreter-core
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40183 |
|---|---|
| Nosy | @Jerome-PS |
| 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 2020-04-04.20:45:48.561>
labels = ['interpreter-core', 'build', '3.9']
title = "AC_COMPILE_IFELSE doesn't work in all cases"
updated_at = <Date 2020-04-04.20:46:55.018>
user = 'https://github.com/Jerome-PS'
bugs.python.org fields:
activity = <Date 2020-04-04.20:46:55.018>
actor = 'python-dev'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2020-04-04.20:45:48.561>
creator = 'jerome.hamm'
dependencies = []
files = []
hgrepos = []
issue_num = 40183
keywords = ['patch']
message_count = 1.0
messages = ['365781']
nosy_count = 2.0
nosy_names = ['python-dev', 'jerome.hamm']
pr_nums = ['19367']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue40183'
versions = ['Python 3.9']
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
Start with the referenced BPO issue 40183 and pull request python/cpython#19367. The issue body does not identify files, tests, or a precise expected fix, so use those references to determine the affected build entry points and completion criteria.
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