Automatically set parent thread idents on thread start
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 | 42552 |
|---|---|
| Nosy | @gaborbernat |
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-12-03.09:49:23.451>
labels = ['3.9', '3.10']
title = 'Automatically set parent thread idents on thread start'
updated_at = <Date 2020-12-03.09:49:23.451>
user = 'https://github.com/gaborbernat'
bugs.python.org fields:
activity = <Date 2020-12-03.09:49:23.451>
actor = 'gaborjbernat'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-12-03.09:49:23.451>
creator = 'gaborjbernat'
dependencies = []
files = []
hgrepos = []
issue_num = 42552
keywords = []
message_count = 1.0
messages = ['382398']
nosy_count = 1.0
nosy_names = ['gaborjbernat']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42552'
versions = ['Python 3.9', '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 no files, tests, or entry points. Start by locating CPython's thread-start implementation and its threading tests, then determine how parent thread identifiers should be captured and exposed. Done means the behavior is specified, implemented, and covered by tests for thread creation and parent relationships.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100