Message117330
Range objects are new in 3.0; they supersede 2.x xrange objects, which are perhaps 10 years old. I do not remember that xrange objects had such attributes. On the other hand, I believe there were requests.
The request, with either implementation, seems reasonable in that range objects could be regarded as iterable slice objects. The differences are that range objects have __getitem__, __iter__, and __reversed__ special methods while slice objects have start, stop, and stop real-only attributes and the indices method. (I could not really understand the last from the doc; I had to experiment.) Starting fresh, we might do with just one class instead of two.
I guess this makes me +0.3 at the moment. |
|
Date |
User |
Action |
Args |
2010-09-24 20:40:21 | terry.reedy | set | recipients:
+ terry.reedy, rhettinger, mark.dickinson, daniel.urban, BreamoreBoy |
2010-09-24 20:40:21 | terry.reedy | set | messageid: <1285360821.81.0.434135183818.issue9896@psf.upfronthosting.co.za> |
2010-09-24 20:40:20 | terry.reedy | link | issue9896 messages |
2010-09-24 20:40:19 | terry.reedy | create | |
|