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: typo in unittest mock docs
Type: behavior Stage: resolved
Components: Documentation Versions: Python 3.9, Python 3.8, Python 3.7, Python 3.6, Python 3.5
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: Arunkumar Mani, docs@python, xtreak
Priority: normal Keywords:

Created on 2019-11-05 15:14 by Arunkumar Mani, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg356039 - (view) Author: Arunkumar Mani (Arunkumar Mani) Date: 2019-11-05 15:14
at various places in the docs for unittest mock[https://docs.python.org/3.7/library/unittest.mock.html#magic-mock], assert is wriiten as assret
msg356040 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2019-11-05 15:44
Can you please add the specific piece of text? There is an illustration to say that it's common mistake to type assret instead of assert with which mock gives a new child mock. This can be made stricter with unsafe mode to detect this typo.
msg356042 - (view) Author: Arunkumar Mani (Arunkumar Mani) Date: 2019-11-05 15:55
my bad. i misread the docs. you are right
History
Date User Action Args
2022-04-11 14:59:22adminsetgithub: 82881
2019-11-05 15:55:06Arunkumar Manisetstatus: open -> closed

messages: + msg356042
stage: resolved
2019-11-05 15:44:23xtreaksetnosy: + xtreak
messages: + msg356040
2019-11-05 15:14:56Arunkumar Manicreate