summaryrefslogtreecommitdiffstats
path: root/Python/dynamic_annotations.c
diff options
context:
space:
mode:
authorGregory P. Smith <greg@krypto.org>2022-04-06 15:06:58 (GMT)
committerGitHub <noreply@github.com>2022-04-06 15:06:58 (GMT)
commitac1fb07b6ecb6b93446484f52894914e5199de63 (patch)
treeb019ab47f7da889711b7f4773ee9f866b1dac32b /Python/dynamic_annotations.c
parentd79f118d044e9b4244b5dfda35448d39202d7f56 (diff)
downloadcpython-ac1fb07b6ecb6b93446484f52894914e5199de63.zip
cpython-ac1fb07b6ecb6b93446484f52894914e5199de63.tar.gz
cpython-ac1fb07b6ecb6b93446484f52894914e5199de63.tar.bz2
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.
Diffstat (limited to 'Python/dynamic_annotations.c')
0 files changed, 0 insertions, 0 deletions