Add a PEP578 audit hook for Asyncio loop stalls
Open
Nobody has claimed this yet.
3.13
topic-asyncio
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 44075 |
|---|---|
| Nosy | @tiran, @asvetlov, @1st1, @zooba, @orf |
| 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 2021-05-08.12:19:46.330>
labels = ['3.11', 'type-feature', 'expert-asyncio']
title = 'Add a PEP578 audit hook for Asyncio loop stalls'
updated_at = <Date 2022-03-19.12:00:57.728>
user = 'https://github.com/orf'
bugs.python.org fields:
activity = <Date 2022-03-19.12:00:57.728>
actor = 'asvetlov'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2021-05-08.12:19:46.330>
creator = 'orf'
dependencies = []
files = []
hgrepos = []
issue_num = 44075
keywords = ['patch']
message_count = 6.0
messages = ['393251', '393253', '393255', '393263', '393267', '415542']
nosy_count = 5.0
nosy_names = ['christian.heimes', 'asvetlov', 'yselivanov', 'steve.dower', 'orf']
pr_nums = ['25990']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue44075'
versions = ['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
The issue concerns asyncio loop stalls and a PEP 578 audit hook; no implementation files or tests are named. Review the referenced python/cpython#25990 pull request and the asyncio component context first. Done means the proposed audit hook is implemented and its behavior is covered, but the work is already in patch review and is not a good first issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100