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 Arfrever, abarry, josh.r, levkivskyi, llllllllll, mark.dickinson, martin.panter, python-dev, r.david.murray, rhettinger, serhiy.storchaka, steven.daprano, taleinat, yselivanov
Date 2016-11-12.08:23:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When I first looked at this a year ago, I thought it seemed like a reasonable idea and might be useful.  Since that time, I've haven't encountered any situations whether this would have improved my or someone else's code.  And now, I can't even dream up any scenarios where ``operator.subscript[3:7:2]`` would be better than ``slice(3, 7, 2)``.   Accordingly, I think we should re-evaluate whether there is any real benefit to be had by adding this to the standard library.  Perhaps, we're better off without it.
Date User Action Args
2016-11-12 08:23:45rhettingersetrecipients: + rhettinger, mark.dickinson, taleinat, Arfrever, steven.daprano, r.david.murray, python-dev, martin.panter, serhiy.storchaka, yselivanov, josh.r, llllllllll, levkivskyi, abarry
2016-11-12 08:23:45rhettingersetmessageid: <>
2016-11-12 08:23:45rhettingerlinkissue24379 messages
2016-11-12 08:23:45rhettingercreate