Guido van Rossum <guido@python.org> writes: > IMO, xrange() must die. > > As a compromise to practicality, it should lose functionality, not > gain any. OK, range() becomes lazy, then? Or is there another plan? -- Dave Abrahams Boost Consulting www.boost-consulting.com