From: Martin v. Löwis Date: Fri, 23 May 2008 19:33:13 +0000 (+0000) Subject: Mention that the leaking of variables from list comprehensions X-Git-Tag: v2.6b1~279 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0b66731ddd57963899441a843248f9c34eaa8c75;p=python Mention that the leaking of variables from list comprehensions is fixed in 3.0. --- diff --git a/Doc/reference/expressions.rst b/Doc/reference/expressions.rst index 1a43599c4e..e393661735 100644 --- a/Doc/reference/expressions.rst +++ b/Doc/reference/expressions.rst @@ -1318,10 +1318,9 @@ groups from right to left). .. rubric:: Footnotes -.. [#] In Python 2.3, a list comprehension "leaks" the control variables of each - ``for`` it contains into the containing scope. However, this behavior is - deprecated, and relying on it will not work once this bug is fixed in a future - release. +.. [#] In Python 2.3 and later releases, a list comprehension "leaks" the control + variables of each ``for`` it contains into the containing scope. However, this + behavior is deprecated, and relying on it will not work in Python 3.0 .. [#] While ``abs(x%y) < abs(y)`` is true mathematically, for floats it may not be true numerically due to roundoff. For example, and assuming a platform on which