Guido van Rossum firstname.lastname@example.org writes:
The bytecode compiler should be clever enough to see that you're writing
for i in range(...): ...
and that there's no definition of range other than the built-in one (this requires a subtle change of language rules); it can then substitute an internal equivalent to xrange().
Ouch! What happens to:
def foo(seq): for x in seq: ...
if xrange dies??