print deadlocks
Open
Nobody has claimed this yet.
3.11
3.12
topic-IO
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46210 |
|---|---|
| Nosy | @notarealdeveloper |
| PRs | |
| 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 = None
closed_at = None
created_at = <Date 2021-12-30.23:26:14.207>
labels = ['3.10', 'type-bug', '3.9', 'expert-IO', '3.11']
title = 'print deadlocks'
updated_at = <Date 2021-12-30.23:39:44.119>
user = 'https://github.com/notarealdeveloper'
bugs.python.org fields:
activity = <Date 2021-12-30.23:39:44.119>
actor = 'notarealdeveloper'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IO']
creation = <Date 2021-12-30.23:26:14.207>
creator = 'notarealdeveloper'
dependencies = []
files = ['50532']
hgrepos = []
issue_num = 46210
keywords = ['patch']
message_count = 1.0
messages = ['409394']
nosy_count = 1.0
nosy_names = ['notarealdeveloper']
pr_nums = ['30310']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue46210'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 linked example.py, which demonstrates the deadlock, and review PR 30310 for the proposed fix. Compare the example's behavior with the affected I/O path and verify that the deadlock no longer occurs; the issue is already under patch review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100