[Python-Dev] Re: More int/long integration issues
Thu, 20 Mar 2003 16:43:51 -0500
Guido van Rossum <email@example.com> writes:
> The bytecode compiler should be clever enough to see that you're
> 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:
for x in seq:
if xrange dies??