Message 63381 - Python tracker

➜

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	exarkun
Recipients	belopolsky, exarkun, gvanrossum, lpd, rhettinger
Date	2008-03-08.03:15:40
SpamBayes Score	0.001772958
Marked as misclassified	No
Message-id	<1204946141.74.0.817295938227.issue1733184@psf.upfronthosting.co.za>
In-reply-to

Content
> Slice objects are really meant to be internal structures and not passed around in the user's code. I don't know what they're "meant" to be, but they're certainly not internal. If you implement __getitem__, __setitem__, or __delitem__, then chances are Python is going to be passing slices to your code. That doesn't sound internal to me. Having hashable slices is nice. The repr() workaround has a major drawback in that it makes it difficult to use the extremely useful "indices" method of the slice type.

> Slice objects are really meant to be internal structures and not
passed around in the user's code. 

I don't know what they're "meant" to be, but they're certainly not
internal.  If you implement __getitem__, __setitem__, or __delitem__,
then chances are Python is going to be passing slices to your code. 
That doesn't sound internal to me.

Having hashable slices is nice.  The repr() workaround has a major
drawback in that it makes it difficult to use the extremely useful
"indices" method of the slice type.

History
Date	User	Action	Args
2008-03-08 03:15:42	exarkun	set	spambayes_score: 0.00177296 -> 0.001772958 recipients: + exarkun, gvanrossum, rhettinger, lpd, belopolsky
2008-03-08 03:15:41	exarkun	set	spambayes_score: 0.00177296 -> 0.00177296 messageid: <1204946141.74.0.817295938227.issue1733184@psf.upfronthosting.co.za>
2008-03-08 03:15:41	exarkun	link	issue1733184 messages
2008-03-08 03:15:40	exarkun	create