Message133921
Now that the moratorium has already ended, I'll try again. I've updated the patch.
It seems, that this idea has already came up in the past: Guido in msg70525 said: "I also think ranges should be introspectable, exposing their start, stop and step values just like slice objects."
A possible use case: the range slicing logic is quite complex (with a lot of corner cases). It would be good, if this logic would be accessible from Python code, for example to compute a slice of a slice-like-thing. Currently slicing a range object returns another range object, but there is no way to determine the bounds of this new object. |
|
Date |
User |
Action |
Args |
2011-04-17 11:51:51 | daniel.urban | set | recipients:
+ daniel.urban, rhettinger, terry.reedy, mark.dickinson, pitrou, BreamoreBoy |
2011-04-17 11:51:51 | daniel.urban | set | messageid: <1303041111.52.0.257045423952.issue9896@psf.upfronthosting.co.za> |
2011-04-17 11:51:50 | daniel.urban | link | issue9896 messages |
2011-04-17 11:51:50 | daniel.urban | create | |
|