Misspelled Assert

[ChrisRao]

BPO	28173
Nosy	@voidspace, @ethanfurman

^{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 = <Date 2016-09-15.19:17:50.391>
created_at = <Date 2016-09-15.19:10:15.274>
labels = ['invalid', 'docs']
title = 'Misspelled Assert'
updated_at = <Date 2016-09-15.19:17:50.381>
user = 'https://bugs.python.org/ChrisRao'

bugs.python.org fields:

activity = <Date 2016-09-15.19:17:50.381>
actor = 'ethan.furman'
assignee = 'docs@python'
closed = True
closed_date = <Date 2016-09-15.19:17:50.391>
closer = 'ethan.furman'
components = ['Documentation']
creation = <Date 2016-09-15.19:10:15.274>
creator = 'Chris Rao'
dependencies = []
files = []
hgrepos = []
issue_num = 28173
keywords = []
message_count = 2.0
messages = ['276596', '276601']
nosy_count = 4.0
nosy_names = ['michael.foord', 'docs@python', 'ethan.furman', 'Chris Rao']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue28173'
versions = []

[ChrisRao]

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)

[ethanfurman]

The misspelling is intentional. That section is talking about what happens when an "assert_" method is misspelled.