RetroSearch Browse

Thu Oct 23 00:17:28 EDT 2003 · https://mail.python.org/pipermail/python-dev/2003-October/039345.html

> Guido:
> > The variable of a for *statement* must be accessible after the loop
> > because you might want to break out of the loop with a specific
> > value.  This is a common pattern that I have no intent of breaking.

[Greg]
> It wouldn't be a great hardship if the loop variable
> weren't accessible after the break, because you can
> always write
> 
>   for x in stuff:
>     if meets_condition(x):
>       result = x
>       break
>   do_something_with(result)
> 
> which is arguably a clearer way to write it, anyway.

I don't know.  It seems to add clutter.  I don't see the big urge to
limit the scope of loop control variables.

--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2003-October/039345.html below:

[Python-Dev] listcomps vs. for loops