➜

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 pitrou
Recipients BreamoreBoy, daniel.urban, mark.dickinson, pitrou, rhettinger, terry.reedy
Date 2010-09-25.13:32:50
SpamBayes Score 0.00011835589
Marked as misclassified No
Message-id <1285421572.87.0.793192705103.issue9896@psf.upfronthosting.co.za>
In-reply-to
Content 
> One other thought.  If there is a perceived need, I would rather an
> alternate approach that unifies a language a bit by letting range()
> expose its arguments as a slice and modify its input to accept a slice.

This sounds like an obscure complication to me. A range is not a slice and I don't see the point of trying to bridge both concepts. It is even more YAGNI than the original request.
History
Date User Action Args
2010-09-25 13:32:53pitrousetrecipients: + pitrou, rhettinger, terry.reedy, mark.dickinson, daniel.urban, BreamoreBoy
2010-09-25 13:32:52pitrousetmessageid: <1285421572.87.0.793192705103.issue9896@psf.upfronthosting.co.za>
2010-09-25 13:32:50pitroulinkissue9896 messages
2010-09-25 13:32:50pitroucreate