Improve the lltrace feature with the Py_Debug mode
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reading the migrated issue thread and reviewing issue25571.patch, issue25571-2.diff, issue25571-3.diff, and issue25571-4.diff. No source entry point or test is named in the issue; done requires an agreed Py_Debug behavior for lltrace and a reviewed, working implementation.
Written by the indexing model from the issue text.
Description
| BPO | 25571 |
|---|---|
| Nosy | @vstinner, @gwk, @matrixise, @Vgr255 |
| 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 = 'https://github.com/vstinner'
closed_at = None
created_at = <Date 2015-11-06.21:13:45.991>
labels = ['interpreter-core', 'type-feature']
title = 'Improve the lltrace feature with the Py_Debug mode'
updated_at = <Date 2017-07-23.13:02:34.149>
user = 'https://github.com/matrixise'
bugs.python.org fields:
activity = <Date 2017-07-23.13:02:34.149>
actor = 'vstinner'
assignee = 'vstinner'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2015-11-06.21:13:45.991>
creator = 'matrixise'
dependencies = []
files = ['40964', '43747', '43992', '43997']
hgrepos = []
issue_num = 25571
keywords = ['patch']
message_count = 20.0
messages = ['254218', '254219', '255347', '270552', '270553', '270859', '270860', '270863', '270864', '271914', '271915', '271931', '271933', '278723', '294378', '294463', '298435', '298438', '298849', '298904']
nosy_count = 6.0
nosy_names = ['vstinner', 'akaptur', 'gwk', 'matrixise', 'xcombelle', 'abarry']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue25571'
versions = ['Python 3.6']
- 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
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·