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 ncoghlan
Recipients mark.dickinson, ncoghlan, serhiy.storchaka, tehybel, terry.reedy
Date 2016-09-09.07:20:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As in, for arguments that have __index__() methods, do the conversion to a true Python integer eagerly when the slice is built rather than lazily when slice.indices() (or the C-level equivalent) is called?

That actually seems like a potentially plausible future approach to me, but isn't a change I'd want to make hastily - those values are visible as the start, stop and step attributes on the slice, and currently describes those as "These attributes can have any type."

Given that folks do a lot of arcane things with the subscript notation, I wouldn't want to break working code if we have less intrusive alternatives.
Date User Action Args
2016-09-09 07:20:49ncoghlansetrecipients: + ncoghlan, terry.reedy, mark.dickinson, serhiy.storchaka, tehybel
2016-09-09 07:20:49ncoghlansetmessageid: <>
2016-09-09 07:20:49ncoghlanlinkissue27867 messages
2016-09-09 07:20:49ncoghlancreate