Mock.call_args and Mock.call_args_list not propagated to parent Mock
Open
Nobody has claimed this yet.
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38505 |
|---|---|
| Nosy | @phmc, @tirkarthi |
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 2019-10-17.12:23:54.924>
labels = []
title = 'Mock.call_args and Mock.call_args_list not propagated to parent Mock'
updated_at = <Date 2019-10-28.20:47:49.330>
user = 'https://bugs.python.org/CarisMoses'
bugs.python.org fields:
activity = <Date 2019-10-28.20:47:49.330>
actor = 'pconnell'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2019-10-17.12:23:54.924>
creator = 'Caris Moses'
dependencies = []
files = []
hgrepos = []
issue_num = 38505
keywords = []
message_count = 1.0
messages = ['354841']
nosy_count = 3.0
nosy_names = ['pconnell', 'xtreak', 'Caris Moses']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue38505'
versions = []
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 identifies Mock.call_args and Mock.call_args_list as the affected behavior, but mentions no source file, test, or entry point. Start by locating the unittest.mock Mock implementation and existing call-tracking tests, then reproduce the parent-child Mock case described by the title. Done means the propagation behavior is corrected and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100