summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris <cbrown119955@gmail.com>2017-12-12 07:59:30 (GMT)
committerAndrew Svetlov <andrew.svetlov@gmail.com>2017-12-12 07:59:30 (GMT)
commite0720cd9e44d43587e6b6c91fd21d0bb0345ccb9 (patch)
treef57c1ce32bdc7b09a94c3590770d8c4a433f3c99
parente570211406f9bfbe16eff8d10e614d90497e08df (diff)
downloadcpython-e0720cd9e44d43587e6b6c91fd21d0bb0345ccb9.zip
cpython-e0720cd9e44d43587e6b6c91fd21d0bb0345ccb9.tar.gz
cpython-e0720cd9e44d43587e6b6c91fd21d0bb0345ccb9.tar.bz2
Fix small typo in tupleobject.h (#4801)
-rw-r--r--Include/tupleobject.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/Include/tupleobject.h b/Include/tupleobject.h
index 98c2622..72a7d8d 100644
--- a/Include/tupleobject.h
+++ b/Include/tupleobject.h
@@ -10,7 +10,7 @@ extern "C" {
/*
Another generally useful object type is a tuple of object pointers.
For Python, this is an immutable type. C code can change the tuple items
-(but not their number), and even use tuples are general-purpose arrays of
+(but not their number), and even use tuples as general-purpose arrays of
object references, but in general only brand new tuples should be mutated,
not ones that might already have been exposed to Python code.