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 docs@python, ezio.melotti, mrabarnett, rhettinger, serhiy.storchaka, timehorse, tlynn
Date 2019-07-13.18:37:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563043052.67.0.337933741369.issue7940@roundup.psfhosted.org>
In-reply-to
Content
-1 on the proposal.  We don't know of any strong use cases, so there isn't a real problem being solved here.  Rather than providing a benefit, this feature request makes it more likely that people will write convoluted code or that it will let bugs pass silently that would otherwise be caught.

ISTM the actual issue here is an incorrect user expectation that "all things that having indexing will support negative indexing".  While it is common for objects to implement negative index support, it is not universal or required.  Even collections.abc.Sequence does not insist on negative index support.

I think this warrants a FAQ entry (which should also mention that slice support as well is not universal or required, some objects have it, some don't).

Reclassifying this as documentation issue.
History
Date User Action Args
2019-07-13 18:37:32rhettingersetrecipients: + rhettinger, tlynn, timehorse, ezio.melotti, mrabarnett, docs@python, serhiy.storchaka
2019-07-13 18:37:32rhettingersetmessageid: <1563043052.67.0.337933741369.issue7940@roundup.psfhosted.org>
2019-07-13 18:37:32rhettingerlinkissue7940 messages
2019-07-13 18:37:32rhettingercreate