]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
bpo-47235: Note where a typo is intentional in code. (GH-32348)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Wed, 6 Apr 2022 15:30:01 +0000 (08:30 -0700)
committerGitHub <noreply@github.com>
Wed, 6 Apr 2022 15:30:01 +0000 (08:30 -0700)
commit3856b4995ec0e632d47b733cdecb5183ac830568
tree5d6ba26f972e4032c62c7936b72c990e031479b2
parent8bce3cb16df5b8ac06ac6b2cae177dd221780b2f
bpo-47235: Note where a typo is intentional in code. (GH-32348)

People keep popping up reporting these as typos in the docs despite
being described as typos in the surrounding text.  Hopefully a comment
on the line itself makes it more obvious?

Arguably some of the typo examples are not using the "right" typo as the
"assret" one in particular is now detected by default due to how common
it was in actual code.  But I don't want to to typo chasing by changing
these examples to be other not yet auto-detected typos as they still
illustrate the point well enough.
(cherry picked from commit ac1fb07b6ecb6b93446484f52894914e5199de63)

Co-authored-by: Gregory P. Smith <greg@krypto.org>
Doc/library/unittest.mock.rst