mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-11 22:55:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Issue #13557: Clarify effect of giving two different namespaces to exec or

Browse source 
execfile().
This commit is contained in:
Terry Jan Reedy 2012-07-08 17:36:14 -04:00
parent 45ce4dc73e
commit 83efd6cbb6
2 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

5
Doc/library/functions.rst
View file

@ -417,7 +417,10 @@ are always available. They are listed here in alphabetical order.
current scope. If only *globals* is provided, it must be a dictionary, which current scope. If only *globals* is provided, it must be a dictionary, which
will be used for both the global and the local variables. If *globals* and will be used for both the global and the local variables. If *globals* and
*locals* are given, they are used for the global and local variables, *locals* are given, they are used for the global and local variables,
respectively. If provided, *locals* can be any mapping object. respectively. If provided, *locals* can be any mapping object. Remember
that at module level, globals and locals are the same dictionary. If exec
gets two separate objects as *globals* and *locals*, the code will be
executed as if it were embedded in a class definition.
If the *globals* dictionary does not contain a value for the key If the *globals* dictionary does not contain a value for the key
``__builtins__``, a reference to the dictionary of the built-in module ``__builtins__``, a reference to the dictionary of the built-in module

6
Misc/NEWS
View file

@ -380,14 +380,14 @@ Build
Documentation Documentation
------------- -------------
- Issue #13557: Clarify effect of giving two different namespaces to exec or
execfile().
- Issue #8799: Fix and improve the threading.Condition documentation. - Issue #8799: Fix and improve the threading.Condition documentation.
- Issue #14943: Correct a default argument value for winreg.OpenKey - Issue #14943: Correct a default argument value for winreg.OpenKey
and correctly list the argument names in the function's explanation. and correctly list the argument names in the function's explanation.
Documentation
-------------
- Issue #14034: added the argparse tutorial. - Issue #14034: added the argparse tutorial.
Tools/Demos Tools/Demos