This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Misspelled Assert
Type: Stage: resolved
Components: Documentation Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Chris Rao, docs@python, ethan.furman, michael.foord
Priority: normal Keywords:

Created on 2016-09-15 19:10 by Chris Rao, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg276596 - (view) Author: Chris Rao (Chris Rao) Date: 2016-09-15 19:10
In the second code block in the section on autospeccing in https://docs.python.org/3/library/unittest.mock.html#auto-speccing, assert is spelled as "assret"

>>> mock = Mock(name='Thing', return_value=None)
>>> mock(1, 2, 3)
>>> mock.assret_called_once_with(4, 5, 6)
msg276601 - (view) Author: Ethan Furman (ethan.furman) * (Python committer) Date: 2016-09-15 19:17
The misspelling is intentional.  That section is talking about what happens when an "assert_" method is misspelled.
History
Date User Action Args
2022-04-11 14:58:36adminsetgithub: 72360
2016-09-15 19:17:50ethan.furmansetstatus: open -> closed

nosy: + ethan.furman, michael.foord
messages: + msg276601

resolution: not a bug
stage: resolved
2016-09-15 19:10:15Chris Raocreate