unittest.mock.patch() cannot properly mock methods
Open
Nobody has claimed this yet.
3.10
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
stdlib
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42556 |
|---|---|
| Nosy | @cjw296, @voidspace, @mariocj89, @tirkarthi, @CendioOssman |
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.14:41:06.568>
labels = ['3.8', '3.7', 'library', '3.9', '3.10']
title = 'unittest.mock.patch() cannot properly mock methods'
updated_at = <Date 2020-12-16.17:12:39.719>
user = 'https://github.com/CendioOssman'
bugs.python.org fields:
activity = <Date 2020-12-16.17:12:39.719>
actor = 'mariocj89'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-12-03.14:41:06.568>
creator = 'CendioOssman'
dependencies = []
files = []
hgrepos = []
issue_num = 42556
keywords = []
message_count = 2.0
messages = ['382415', '383189']
nosy_count = 5.0
nosy_names = ['cjw296', 'michael.foord', 'mariocj89', 'xtreak', 'CendioOssman']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42556'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', '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
Begin with the unittest.mock.patch() entry point and the original BPO issue 42556. The payload names no source file, test, reproduction, or expected behavior, so first clarify how method mocking currently fails and what behavior should be preserved; done should include an agreed regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100