Mercurial > cpython-lru_cache-weakref
diff Doc/api/api.tex @ 15038:e9713cbe2ba8 legacy-trunk
The _PyTuple_Resize() last_is_sticky flag must now always be false.
| author | Neil Schemenauer <nascheme@enme.ucalgary.ca> |
|---|---|
| date | Thu, 05 Oct 2000 19:38:24 +0000 |
| parents | 76c1e40c5c5d |
| children | a13a2acbe214 |
line wrap: on
line diff
--- a/Doc/api/api.tex Thu Oct 05 19:36:49 2000 +0000 +++ b/Doc/api/api.tex Thu Oct 05 19:38:24 2000 +0000 @@ -3070,12 +3070,12 @@ 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}
