RetroSearch Browse

Tue Oct 21 14:57:49 EDT 2003 · https://mail.python.org/pipermail/python-dev/2003-October/039163.html

On Tue, Oct 21, 2003, Guido van Rossum wrote:
>
> It's only list comprehensions where I plan to remove x from the scope
> after the comprehension is finished.
> 
> Do you need a warning for that change too?  Code that relies on it is
> pretty sick IMO.

Yes, it's sick, but since you made clear previously that listcomps
semantics equivalent to the corresponding for loop, I wouldn't be
surprised to discover that someone converted a for loop to a listcomp
without fixing that sickness.  So yes, it needs a warning.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"It is easier to optimize correct code than to correct optimized code."
--Bill Harlan

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

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

[Python-Dev] listcomps vs. for loops