_tracemalloc.c and Clang-cl
Open
Nobody has claimed this yet.
3.10
build
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42078 |
|---|---|
| Nosy | @gvanem |
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-10-19.07:03:42.269>
labels = ['build', '3.10']
title = '_tracemalloc.c and Clang-cl'
updated_at = <Date 2020-10-19.07:03:42.269>
user = 'https://github.com/gvanem'
bugs.python.org fields:
activity = <Date 2020-10-19.07:03:42.269>
actor = 'gvanem'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build']
creation = <Date 2020-10-19.07:03:42.269>
creator = 'gvanem'
dependencies = []
files = []
hgrepos = []
issue_num = 42078
keywords = []
message_count = 1.0
messages = ['378928']
nosy_count = 1.0
nosy_names = ['gvanem']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'compile error'
url = 'https://bugs.python.org/issue42078'
versions = ['Python 3.10']
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
The issue names _tracemalloc.c and Clang-cl but provides no error details or test location. Begin by reproducing the compile failure with Clang-cl and inspecting _tracemalloc.c; done means the file builds successfully with that compiler and the relevant build check passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100