improve tracing performance with f_trace set to Py_None
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27218 |
|---|---|
| Nosy | @birkenfeld, @xdegaye, @serhiy-storchaka |
| 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 2016-06-04.16:27:47.484>
labels = ['type-feature', 'library']
title = 'improve tracing performance with f_trace set to Py_None'
updated_at = <Date 2019-09-15.13:23:40.914>
user = 'https://github.com/xdegaye'
bugs.python.org fields:
activity = <Date 2019-09-15.13:23:40.914>
actor = 'nanjekyejoannah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-06-04.16:27:47.484>
creator = 'xdegaye'
dependencies = []
files = []
hgrepos = []
issue_num = 27218
keywords = ['patch']
message_count = 1.0
messages = ['267262']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'xdegaye', 'serhiy.storchaka']
pr_nums = ['16157']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue27218'
versions = ['Python 3.6']
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 points to BPO 27218 and the migrated PR python/cpython#16157; start by reviewing that PR and its discussion. No source file, test, or entry point is named in the issue, so the implementation and completion criteria must be recovered from the existing work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100