Daniel Urban <urban.dani...@gmail.com> added the comment: 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. ---------- versions: +Python 3.3 -Python 3.2 Added file: http://bugs.python.org/file21692/range_attrs_2.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9896> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
