Xavier Morel wrote: > While xrange does have it's place in Python, it has very few actual uses > (yours being one of the few), and is usually more harmful than beneficial. > > While the deprecation of xrange is not that "soon", it is part of the > Python 3000 PEP (http://www.python.org/peps/pep-3000.html#id38) along > with the deprecation of most FP-facilities of Python (filter, map, reduce). > > It should also be noted that reimplementing xrange when needed is > trivial and can be done with a 5-lines generator for the minimal version > (1 argument, 0-n range) and probably less than 10 lines for the full > blown version equivalent to the current one (including start, end and > step arguments)
Seems that xrange() would be deprecated because range() will be the lazy version, so a name change or more like that the current range(), i.e. the one that returns a list will be deprecated, feature wise. -- http://mail.python.org/mailman/listinfo/python-list
