From 410cb6be8f15b102caddce0e70bbe4cb37ec24e9 Mon Sep 17 00:00:00 2001 From: Neil Schemenauer Date: Thu, 5 Oct 2000 19:38:24 +0000 Subject: The _PyTuple_Resize() last_is_sticky flag must now always be false. --- Doc/api/api.tex | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Doc/api/api.tex b/Doc/api/api.tex index 53ca462..83f624d 100644 --- a/Doc/api/api.tex +++ b/Doc/api/api.tex @@ -3070,12 +3070,12 @@ Can be used to resize a tuple. \var{newsize} will be the new length of the tuple. Because tuples are \emph{supposed} to be immutable, this should only be used if there is only one reference to the object. Do \emph{not} use this if the tuple may already be known to some other -part of the code. \var{last_is_sticky} is a flag --- if true, the -tuple will grow or shrink at the front, otherwise it will grow or -shrink at the end. Think of this as destroying the old tuple and -creating a new one, only more efficiently. Returns \code{0} on -success and \code{-1} on failure (in which case a -\exception{MemoryError} or \exception{SystemError} will be raised). +part of the code. The tuple will always grow or shrink at the end. The +\var{last_is_sticky} flag is not used and should always be false. Think +of this as destroying the old tuple and creating a new one, only more +efficiently. Returns \code{0} on success and \code{-1} on failure (in +which case a \exception{MemoryError} or \exception{SystemError} will be +raised). \end{cfuncdesc} -- cgit v0.12