From 0ee1467704e0c6012df3b4da6dfceeaf61bc701d Mon Sep 17 00:00:00 2001 From: "R. David Murray" Date: Sat, 14 Nov 2009 22:28:36 +0000 Subject: [PATCH] Merged revisions 76272 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r76272 | r.david.murray | 2009-11-14 17:27:22 -0500 (Sat, 14 Nov 2009) | 2 lines Fix print function conversion missed in merge of faq/programming update. ........ --- Doc/faq/programming.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/faq/programming.rst b/Doc/faq/programming.rst index 0bc94118951..e2e6f92ab12 100644 --- a/Doc/faq/programming.rst +++ b/Doc/faq/programming.rst @@ -310,7 +310,7 @@ This is because when you make an assignment to a variable in a scope, that variable becomes local to that scope and shadows any similarly named variable in the outer scope. Since the last statement in foo assigns a new value to ``x``, the compiler recognizes it as a local variable. Consequently when the -earlier ``print x`` attempts to print the uninitialized local variable and +earlier ``print(x)`` attempts to print the uninitialized local variable and an error results. In the example above you can access the outer scope variable by declaring it