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.

Author Mariatta
Recipients Mariatta, docs@python
Date 2022-04-05.22:46:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1649198769.94.0.805026141496.issue47235@roundup.psfhosted.org>
In-reply-to
Content
In unittest.mock documentation, there is an example code which intentionally contains typo.

Source: https://github.com/python/cpython/blame/main/Doc/library/unittest.mock.rst#L2553

We've received quite a number of false "bug report" regarding this text. Basically people saw the sample code containing `assret` then they rushed to create an issue/PR, before actually reading the rest of the section. This typo was intentionally placed there, so it should not be fixed. However since this is definitely confusing to readers, perhaps the documentation should be improved.

On Discord, Brandt suggested to add a comment on the sample code like:


```
# Intended typo!
```

so hopefully people will stop trying to fix it.


Previous false "bug reports":
bpo-35789
bpo-38700
History
Date User Action Args
2022-04-05 22:46:10Mariattasetrecipients: + Mariatta, docs@python
2022-04-05 22:46:09Mariattasetmessageid: <1649198769.94.0.805026141496.issue47235@roundup.psfhosted.org>
2022-04-05 22:46:09Mariattalinkissue47235 messages
2022-04-05 22:46:09Mariattacreate