Cryptic error message if incorrect spec is set on a callable mock

Open
#69,499 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

The issue names Python callable mocks and an incorrect-spec failure, but no file or test. Start by reproducing that case and locating where the cryptic error is produced; done means the failure is clearly reported and regression coverage verifies the improved behavior.

Written by the indexing model from the issue text.

Description

3.7 (EOL) 3.8 (EOL) 3.9 (EOL) stdlib type-bug
BPO 25312
Nosy @cjw296, @voidspace, @uranusjr, @mariocj89, @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 2015-10-04.18:07:08.628>
labels = ['3.7', '3.8', 'type-bug', 'library', '3.9']
title = 'Cryptic error message if incorrect spec is set on a callable mock'
updated_at = <Date 2019-08-01.05:43:20.709>
user = 'https://github.com/uranusjr'

bugs.python.org fields:

activity = <Date 2019-08-01.05:43:20.709>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-10-04.18:07:08.628>
creator = 'uranusjr'
dependencies = []
files = []
hgrepos = []
issue_num = 25312
keywords = []
message_count = 2.0
messages = ['252276', '348840']
nosy_count = 5.0
nosy_names = ['cjw296', 'michael.foord', 'uranusjr', 'mariocj89', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25312'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.