Exception in AsyncMock side_effect cases incorrect refcount
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 44410 |
|---|---|
| Nosy | @asvetlov, @1st1, @Penlect |
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-06-13.14:52:01.808>
labels = ['type-bug', '3.9', 'expert-asyncio']
title = 'Exception in AsyncMock side_effect cases incorrect refcount'
updated_at = <Date 2021-06-13.14:52:01.808>
user = 'https://github.com/Penlect'
bugs.python.org fields:
activity = <Date 2021-06-13.14:52:01.808>
actor = 'penlect'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2021-06-13.14:52:01.808>
creator = 'penlect'
dependencies = []
files = []
hgrepos = []
issue_num = 44410
keywords = []
message_count = 1.0
messages = ['395752']
nosy_count = 3.0
nosy_names = ['asvetlov', 'yselivanov', 'penlect']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44410'
versions = ['Python 3.9']
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 BPO issue 44410 and inspect the AsyncMock side_effect behavior in the asyncio-related implementation and tests. Reproduce the exception cases and trace their reference counts; done means the affected cases maintain correct reference counts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100