This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients MSeifert, docs@python, rhettinger, xiang.zhang
Date 2017-03-15.04:25:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489551920.87.0.159891195927.issue29813@psf.upfronthosting.co.za>
In-reply-to
Content
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."
History
Date User Action Args
2017-03-15 04:25:20rhettingersetrecipients: + rhettinger, docs@python, xiang.zhang, MSeifert
2017-03-15 04:25:20rhettingersetmessageid: <1489551920.87.0.159891195927.issue29813@psf.upfronthosting.co.za>
2017-03-15 04:25:20rhettingerlinkissue29813 messages
2017-03-15 04:25:20rhettingercreate