[issue29813] PyTuple_GetSlice does not always return a new tuple

Raymond Hettinger report at bugs.python.org
Wed Mar 15 00:25:20 EDT 2017


Raymond Hettinger added the comment:

I think the docs are fine as-is.  Whether an identical tuple is new or not is an implementation detail.

IMO, the docs would create more confusion by trying to over-explain, "slicing of tuples always returns a new tuple when the result tuple is distinct from the original; however, in the case where the result tuple is not distinct, the implementation is at liberty to return the original tuple instead of a new tuple.  Since tuples are immutable, this should make no difference at all to the user."

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue29813>
_______________________________________


More information about the Python-bugs-list mailing list