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 llllllllll
Recipients Arfrever, llllllllll, mark.dickinson, rhettinger, serhiy.storchaka, steven.daprano
Date 2015-06-04.13:32:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433424753.73.0.300647009519.issue24379@psf.upfronthosting.co.za>
In-reply-to
Content
> Why not index the slice type itself? slice[1:2]

I originally considered this and I personally really like this syntax, but I was concerned with ambiguity with the typing module

> The only question in my mind is what slice should do when given just a single index

I think some of the power of this concept comes from the fact that I can express a complicated indexer without worrying about how it desugars. I would personally prefer being able to have this return tuples and scalars so that the syntax is easier to explain.
History
Date User Action Args
2015-06-04 13:32:33llllllllllsetrecipients: + llllllllll, rhettinger, mark.dickinson, Arfrever, steven.daprano, serhiy.storchaka
2015-06-04 13:32:33llllllllllsetmessageid: <1433424753.73.0.300647009519.issue24379@psf.upfronthosting.co.za>
2015-06-04 13:32:33lllllllllllinkissue24379 messages
2015-06-04 13:32:33llllllllllcreate