]> 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:32:16 +0000 (08:32 -0700)
committerGitHub <noreply@github.com>
Wed, 6 Apr 2022 15:32:16 +0000 (08:32 -0700)
commit770780e63e2a99f842670ef901a257ba64293d6b
treee8301a8d64b3b0b3c7d0a6b717ef9def201ab4f5
parenta4c7752f3e00b75fd1e4603458b8c77a9fa3d4cb
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