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 daniel.urban
Recipients BreamoreBoy, daniel.urban, mark.dickinson, pitrou, rhettinger, terry.reedy
Date 2011-04-17.11:51:50
SpamBayes Score 5.4229065e-07
Marked as misclassified No
Message-id <>
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:51daniel.urbansetrecipients: + daniel.urban, rhettinger, terry.reedy, mark.dickinson, pitrou, BreamoreBoy
2011-04-17 11:51:51daniel.urbansetmessageid: <>
2011-04-17 11:51:50daniel.urbanlinkissue9896 messages
2011-04-17 11:51:50daniel.urbancreate