traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

exec won't take file objects anymore

This commit is contained in:
Benjamin Peterson 2008-11-11 21:43:42 +00:00
parent 3e4e72f66f
commit d3013ffa49
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Doc/library/functions.rst
View File

@ -391,16 +391,15 @@ are always available. They are listed here in alphabetical order.
.. function:: exec(object[, globals[, locals]])
This function supports dynamic execution of Python code. *object* must be either
a string, an open file object, or a code object. If it is a string, the string
is parsed as a suite of Python statements which is then executed (unless a
syntax error occurs). If it is an open file, the file is parsed until EOF and
executed. If it is a code object, it is simply executed. In all cases, the
This function supports dynamic execution of Python code. *object* must be
either a string or a code object. If it is a string, the string is parsed as
a suite of Python statements which is then executed (unless a syntax error
occurs). If it is a code object, it is simply executed. In all cases, the
code that's executed is expected to be valid as file input (see the section
"File input" in the Reference Manual). Be aware that the :keyword:`return` and
:keyword:`yield` statements may not be used outside of function definitions even
within the context of code passed to the :func:`exec` function. The return value
is ``None``.
"File input" in the Reference Manual). Be aware that the :keyword:`return`
and :keyword:`yield` statements may not be used outside of function
definitions even within the context of code passed to the :func:`exec`
function. The return value is ``None``.
In all cases, if the optional parts are omitted, the code is executed in the
current scope. If only *globals* is provided, it must be a dictionary, which