gh-48496: Added example and link to faq for UnboundLocalError in reference (#93068)

diff --git a/Doc/faq/programming.rst b/Doc/faq/programming.rst
index 584d33e9622e333b9e4a5e9682586b157f6bb80b..c396e2b081fca3fd7958e4ae975c685b97f1817d 100644 (file)
--- a/Doc/faq/programming.rst
+++ b/Doc/faq/programming.rst
@@ -113,6 +113,8 @@ Yes.  The coding style required for standard library modules is documented as
 Core Language
 =============
 
+.. _faq-unboundlocalerror:
+
 Why am I getting an UnboundLocalError when the variable has a value?
 --------------------------------------------------------------------
 

diff --git a/Doc/reference/executionmodel.rst b/Doc/reference/executionmodel.rst
index 3f01180e13f776614d9bd3041e114f447e054dcd..a264015cbf40496cad634928dddeda8e497ff6ca 100644 (file)
--- a/Doc/reference/executionmodel.rst
+++ b/Doc/reference/executionmodel.rst
@@ -128,6 +128,8 @@ lead to errors when a name is used within a block before it is bound.  This rule
 is subtle.  Python lacks declarations and allows name binding operations to
 occur anywhere within a code block.  The local variables of a code block can be
 determined by scanning the entire text of the block for name binding operations.
+See :ref:`the FAQ entry on UnboundLocalError <faq-unboundlocalerror>`
+for examples.
 
 If the :keyword:`global` statement occurs within a block, all uses of the names
 specified in the statement refer to the bindings of those names in the top-level