cpython/Doc/c-api/veryhigh.rst

324 lines
13 KiB
ReStructuredText
Raw Normal View History

2007-08-15 11:28:01 -03:00
.. highlightlang:: c
.. _veryhigh:
*************************
The Very High Level Layer
*************************
The functions in this chapter will let you execute Python source code given in a
file or a buffer, but they will not let you interact in a more detailed way with
the interpreter.
Several of these functions accept a start symbol from the grammar as a
parameter. The available start symbols are :const:`Py_eval_input`,
:const:`Py_file_input`, and :const:`Py_single_input`. These are described
following the functions which accept them as parameters.
2012-01-14 11:42:02 -04:00
Note also that several of these functions take :c:type:`FILE\*` parameters. One
particular issue which needs to be handled carefully is that the :c:type:`FILE`
2007-08-15 11:28:01 -03:00
structure for different C libraries can be different and incompatible. Under
Windows (at least), it is possible for dynamically linked extensions to actually
2012-01-14 11:42:02 -04:00
use different libraries, so care should be taken that :c:type:`FILE\*` parameters
2007-08-15 11:28:01 -03:00
are only passed to these functions if it is certain that they were created by
the same library that the Python runtime is using.
2012-01-14 11:42:02 -04:00
.. c:function:: int Py_Main(int argc, char **argv)
2007-08-15 11:28:01 -03:00
The main program for the standard interpreter. This is made available for
programs which embed Python. The *argc* and *argv* parameters should be
2012-01-14 11:42:02 -04:00
prepared exactly as those which are passed to a C program's :c:func:`main`
2007-08-15 11:28:01 -03:00
function. It is important to note that the argument list may be modified (but
the contents of the strings pointed to by the argument list are not). The return
2011-07-29 06:43:47 -03:00
value will be ``0`` if the interpreter exits normally (ie, without an
exception), ``1`` if the interpreter exits due to an exception, or ``2``
if the parameter list does not represent a valid Python command line.
2007-08-15 11:28:01 -03:00
Note that if an otherwise unhandled :exc:`SystemExit` is raised, this
function will not return ``1``, but exit the process, as long as
``Py_InspectFlag`` is not set.
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_AnyFile(FILE *fp, const char *filename)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
*closeit* set to ``0`` and *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_AnyFileFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
the *closeit* argument set to ``0``.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_AnyFileEx(FILE *fp, const char *filename, int closeit)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
the *flags* argument set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_AnyFileExFlags(FILE *fp, const char *filename, int closeit, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
If *fp* refers to a file associated with an interactive device (console or
terminal input or Unix pseudo-terminal), return the value of
2012-01-14 11:42:02 -04:00
:c:func:`PyRun_InteractiveLoop`, otherwise return the result of
:c:func:`PyRun_SimpleFile`. If *filename* is *NULL*, this function uses
2007-08-15 11:28:01 -03:00
``"???"`` as the filename.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleString(const char *command)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_SimpleStringFlags` below,
2007-08-15 11:28:01 -03:00
leaving the *PyCompilerFlags\** argument set to NULL.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleStringFlags(const char *command, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
Executes the Python source code from *command* in the :mod:`__main__` module
according to the *flags* argument. If :mod:`__main__` does not already exist, it
is created. Returns ``0`` on success or ``-1`` if an exception was raised. If
there was an error, there is no way to get the exception information. For the
meaning of *flags*, see below.
Note that if an otherwise unhandled :exc:`SystemExit` is raised, this
function will not return ``-1``, but exit the process, as long as
``Py_InspectFlag`` is not set.
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleFile(FILE *fp, const char *filename)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_SimpleFileExFlags` below,
2007-08-15 11:28:01 -03:00
leaving *closeit* set to ``0`` and *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleFileFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_SimpleFileExFlags` below,
2007-08-15 11:28:01 -03:00
leaving *closeit* set to ``0``.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleFileEx(FILE *fp, const char *filename, int closeit)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_SimpleFileExFlags` below,
2007-08-15 11:28:01 -03:00
leaving *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_SimpleFileExFlags(FILE *fp, const char *filename, int closeit, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
Similar to :c:func:`PyRun_SimpleStringFlags`, but the Python source code is read
2007-08-15 11:28:01 -03:00
from *fp* instead of an in-memory string. *filename* should be the name of the
file. If *closeit* is true, the file is closed before PyRun_SimpleFileExFlags
returns.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_InteractiveOne(FILE *fp, const char *filename)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_InteractiveOneFlags` below,
2007-08-15 11:28:01 -03:00
leaving *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_InteractiveOneFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
Merged revisions 85617-85622,85624,85626-85627,85629,85631,85635-85636,85638-85639,85641-85642 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r85617 | georg.brandl | 2010-10-17 12:09:06 +0200 (So, 17 Okt 2010) | 1 line #5212: md5 weaknesses do not affect hmac, so remove the note about that. ........ r85618 | georg.brandl | 2010-10-17 12:14:38 +0200 (So, 17 Okt 2010) | 1 line #9086: correct wrong terminology about linking with pythonXY.dll. ........ r85619 | georg.brandl | 2010-10-17 12:15:50 +0200 (So, 17 Okt 2010) | 1 line Make file names consistent. ........ r85620 | georg.brandl | 2010-10-17 12:22:28 +0200 (So, 17 Okt 2010) | 1 line Remove second parser module example; it referred to non-readily-available example files, and this kind of discovery is much better done with the AST nowadays anyway. ........ r85621 | georg.brandl | 2010-10-17 12:24:54 +0200 (So, 17 Okt 2010) | 1 line #9105: move pickle warning to a bit more prominent location. ........ r85622 | georg.brandl | 2010-10-17 12:28:04 +0200 (So, 17 Okt 2010) | 1 line #9112: document error() and exit() methods of ArgumentParser. ........ r85624 | georg.brandl | 2010-10-17 12:34:28 +0200 (So, 17 Okt 2010) | 1 line Some markup and style fixes in argparse docs. ........ r85626 | georg.brandl | 2010-10-17 12:38:20 +0200 (So, 17 Okt 2010) | 1 line #9117: fix syntax for class definition. ........ r85627 | georg.brandl | 2010-10-17 12:44:11 +0200 (So, 17 Okt 2010) | 1 line #9138: reword introduction to classes in Python. ........ r85629 | georg.brandl | 2010-10-17 12:51:45 +0200 (So, 17 Okt 2010) | 1 line #5962: clarify sys.exit() vs. threads. ........ r85631 | georg.brandl | 2010-10-17 12:53:54 +0200 (So, 17 Okt 2010) | 1 line Fix capitalization. ........ r85635 | georg.brandl | 2010-10-17 13:03:22 +0200 (So, 17 Okt 2010) | 1 line #5121: fix claims about default values leading to segfaults. ........ r85636 | georg.brandl | 2010-10-17 13:06:14 +0200 (So, 17 Okt 2010) | 1 line #9237: document sys.call_tracing(). ........ r85638 | georg.brandl | 2010-10-17 13:13:37 +0200 (So, 17 Okt 2010) | 1 line Port changes to pickle docs apparently lost in py3k. ........ r85639 | georg.brandl | 2010-10-17 13:23:56 +0200 (So, 17 Okt 2010) | 1 line Make twisted example a bit more logical. ........ r85641 | georg.brandl | 2010-10-17 13:29:07 +0200 (So, 17 Okt 2010) | 1 line Fix documentation of dis.opmap direction. ........ r85642 | georg.brandl | 2010-10-17 13:36:28 +0200 (So, 17 Okt 2010) | 1 line #9730: fix example. ........
2010-11-26 03:53:50 -04:00
Read and execute a single statement from a file associated with an
interactive device according to the *flags* argument. The user will be
prompted using ``sys.ps1`` and ``sys.ps2``. Returns ``0`` when the input was
executed successfully, ``-1`` if there was an exception, or an error code
from the :file:`errcode.h` include file distributed as part of Python if
there was a parse error. (Note that :file:`errcode.h` is not included by
:file:`Python.h`, so must be included specifically if needed.)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_InteractiveLoop(FILE *fp, const char *filename)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_InteractiveLoopFlags` below,
2007-08-15 11:28:01 -03:00
leaving *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyRun_InteractiveLoopFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
Read and execute statements from a file associated with an interactive device
Merged revisions 85617-85622,85624,85626-85627,85629,85631,85635-85636,85638-85639,85641-85642 via svnmerge from svn+ssh://pythondev@svn.python.org/python/branches/py3k ........ r85617 | georg.brandl | 2010-10-17 12:09:06 +0200 (So, 17 Okt 2010) | 1 line #5212: md5 weaknesses do not affect hmac, so remove the note about that. ........ r85618 | georg.brandl | 2010-10-17 12:14:38 +0200 (So, 17 Okt 2010) | 1 line #9086: correct wrong terminology about linking with pythonXY.dll. ........ r85619 | georg.brandl | 2010-10-17 12:15:50 +0200 (So, 17 Okt 2010) | 1 line Make file names consistent. ........ r85620 | georg.brandl | 2010-10-17 12:22:28 +0200 (So, 17 Okt 2010) | 1 line Remove second parser module example; it referred to non-readily-available example files, and this kind of discovery is much better done with the AST nowadays anyway. ........ r85621 | georg.brandl | 2010-10-17 12:24:54 +0200 (So, 17 Okt 2010) | 1 line #9105: move pickle warning to a bit more prominent location. ........ r85622 | georg.brandl | 2010-10-17 12:28:04 +0200 (So, 17 Okt 2010) | 1 line #9112: document error() and exit() methods of ArgumentParser. ........ r85624 | georg.brandl | 2010-10-17 12:34:28 +0200 (So, 17 Okt 2010) | 1 line Some markup and style fixes in argparse docs. ........ r85626 | georg.brandl | 2010-10-17 12:38:20 +0200 (So, 17 Okt 2010) | 1 line #9117: fix syntax for class definition. ........ r85627 | georg.brandl | 2010-10-17 12:44:11 +0200 (So, 17 Okt 2010) | 1 line #9138: reword introduction to classes in Python. ........ r85629 | georg.brandl | 2010-10-17 12:51:45 +0200 (So, 17 Okt 2010) | 1 line #5962: clarify sys.exit() vs. threads. ........ r85631 | georg.brandl | 2010-10-17 12:53:54 +0200 (So, 17 Okt 2010) | 1 line Fix capitalization. ........ r85635 | georg.brandl | 2010-10-17 13:03:22 +0200 (So, 17 Okt 2010) | 1 line #5121: fix claims about default values leading to segfaults. ........ r85636 | georg.brandl | 2010-10-17 13:06:14 +0200 (So, 17 Okt 2010) | 1 line #9237: document sys.call_tracing(). ........ r85638 | georg.brandl | 2010-10-17 13:13:37 +0200 (So, 17 Okt 2010) | 1 line Port changes to pickle docs apparently lost in py3k. ........ r85639 | georg.brandl | 2010-10-17 13:23:56 +0200 (So, 17 Okt 2010) | 1 line Make twisted example a bit more logical. ........ r85641 | georg.brandl | 2010-10-17 13:29:07 +0200 (So, 17 Okt 2010) | 1 line Fix documentation of dis.opmap direction. ........ r85642 | georg.brandl | 2010-10-17 13:36:28 +0200 (So, 17 Okt 2010) | 1 line #9730: fix example. ........
2010-11-26 03:53:50 -04:00
until EOF is reached. The user will be prompted using ``sys.ps1`` and
``sys.ps2``. Returns ``0`` at EOF.
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
.. c:function:: struct _node* PyParser_SimpleParseString(const char *str, int start)
2007-08-15 11:28:01 -03:00
This is a simplified interface to
2012-01-14 11:42:02 -04:00
:c:func:`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set
2007-08-15 11:28:01 -03:00
to *NULL* and *flags* set to ``0``.
2012-01-14 11:42:02 -04:00
.. c:function:: struct _node* PyParser_SimpleParseStringFlags( const char *str, int start, int flags)
2007-08-15 11:28:01 -03:00
This is a simplified interface to
2012-01-14 11:42:02 -04:00
:c:func:`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set
2007-08-15 11:28:01 -03:00
to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: struct _node* PyParser_SimpleParseStringFlagsFilename( const char *str, const char *filename, int start, int flags)
2007-08-15 11:28:01 -03:00
Parse Python source code from *str* using the start token *start* according to
the *flags* argument. The result can be used to create a code object which can
be evaluated efficiently. This is useful if a code fragment must be evaluated
many times.
2012-01-14 11:42:02 -04:00
.. c:function:: struct _node* PyParser_SimpleParseFile(FILE *fp, const char *filename, int start)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyParser_SimpleParseFileFlags` below,
2007-08-15 11:28:01 -03:00
leaving *flags* set to ``0``
2012-01-14 11:42:02 -04:00
.. c:function:: struct _node* PyParser_SimpleParseFileFlags(FILE *fp, const char *filename, int start, int flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
Similar to :c:func:`PyParser_SimpleParseStringFlagsFilename`, but the Python
2007-08-15 11:28:01 -03:00
source code is read from *fp* instead of an in-memory string.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_String(const char *str, int start, PyObject *globals, PyObject *locals)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_StringFlags` below, leaving
2007-08-15 11:28:01 -03:00
*flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_StringFlags(const char *str, int start, PyObject *globals, PyObject *locals, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
Execute Python source code from *str* in the context specified by the
dictionaries *globals* and *locals* with the compiler flags specified by
*flags*. The parameter *start* specifies the start token that should be used to
parse the source code.
Returns the result of executing the code as a Python object, or *NULL* if an
exception was raised.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_File(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
*closeit* set to ``0`` and *flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_FileEx(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, int closeit)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
*flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_FileFlags(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving
2007-08-15 11:28:01 -03:00
*closeit* set to ``0``.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyRun_FileExFlags(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, int closeit, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
Similar to :c:func:`PyRun_StringFlags`, but the Python source code is read from
2007-08-15 11:28:01 -03:00
*fp* instead of an in-memory string. *filename* should be the name of the file.
2012-01-14 11:42:02 -04:00
If *closeit* is true, the file is closed before :c:func:`PyRun_FileExFlags`
2007-08-15 11:28:01 -03:00
returns.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* Py_CompileString(const char *str, const char *filename, int start)
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`Py_CompileStringFlags` below, leaving
2007-08-15 11:28:01 -03:00
*flags* set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* Py_CompileStringFlags(const char *str, const char *filename, int start, PyCompilerFlags *flags)
2007-08-15 11:28:01 -03:00
Parse and compile the Python source code in *str*, returning the resulting code
object. The start token is given by *start*; this can be used to constrain the
code which can be compiled and should be :const:`Py_eval_input`,
:const:`Py_file_input`, or :const:`Py_single_input`. The filename specified by
*filename* is used to construct the code object and may appear in tracebacks or
:exc:`SyntaxError` exception messages. This returns *NULL* if the code cannot
be parsed or compiled.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyEval_EvalCode(PyCodeObject *co, PyObject *globals, PyObject *locals)
2012-01-14 11:42:02 -04:00
This is a simplified interface to :c:func:`PyEval_EvalCodeEx`, with just
the code object, and the dictionaries of global and local variables.
The other arguments are set to *NULL*.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyEval_EvalCodeEx(PyCodeObject *co, PyObject *globals, PyObject *locals, PyObject **args, int argcount, PyObject **kws, int kwcount, PyObject **defs, int defcount, PyObject *closure)
Evaluate a precompiled code object, given a particular environment for its
evaluation. This environment consists of dictionaries of global and local
variables, arrays of arguments, keywords and defaults, and a closure tuple of
cells.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyEval_EvalFrame(PyFrameObject *f)
Evaluate an execution frame. This is a simplified interface to
PyEval_EvalFrameEx, for backward compatibility.
2012-01-14 11:42:02 -04:00
.. c:function:: PyObject* PyEval_EvalFrameEx(PyFrameObject *f, int throwflag)
This is the main, unvarnished function of Python interpretation. It is
literally 2000 lines long. The code object associated with the execution
frame *f* is executed, interpreting bytecode and executing calls as needed.
The additional *throwflag* parameter can mostly be ignored - if true, then
it causes an exception to immediately be thrown; this is used for the
:meth:`~generator.throw` methods of generator objects.
2012-01-14 11:42:02 -04:00
.. c:function:: int PyEval_MergeCompilerFlags(PyCompilerFlags *cf)
This function changes the flags of the current evaluation frame, and returns
true on success, false on failure.
2012-01-14 11:42:02 -04:00
.. c:var:: int Py_eval_input
2007-08-15 11:28:01 -03:00
.. index:: single: Py_CompileString()
The start symbol from the Python grammar for isolated expressions; for use with
2012-01-14 11:42:02 -04:00
:c:func:`Py_CompileString`.
2007-08-15 11:28:01 -03:00
2012-01-14 11:42:02 -04:00
.. c:var:: int Py_file_input
2007-08-15 11:28:01 -03:00
.. index:: single: Py_CompileString()
The start symbol from the Python grammar for sequences of statements as read
2012-01-14 11:42:02 -04:00
from a file or other source; for use with :c:func:`Py_CompileString`. This is
2007-08-15 11:28:01 -03:00
the symbol to use when compiling arbitrarily long Python source code.
2012-01-14 11:42:02 -04:00
.. c:var:: int Py_single_input
2007-08-15 11:28:01 -03:00
.. index:: single: Py_CompileString()
The start symbol from the Python grammar for a single statement; for use with
2012-01-14 11:42:02 -04:00
:c:func:`Py_CompileString`. This is the symbol used for the interactive
2007-08-15 11:28:01 -03:00
interpreter loop.
2012-01-14 11:42:02 -04:00
.. c:type:: struct PyCompilerFlags
2007-08-15 11:28:01 -03:00
This is the structure used to hold compiler flags. In cases where code is only
being compiled, it is passed as ``int flags``, and in cases where code is being
executed, it is passed as ``PyCompilerFlags *flags``. In this case, ``from
__future__ import`` can modify *flags*.
Whenever ``PyCompilerFlags *flags`` is *NULL*, :attr:`cf_flags` is treated as
equal to ``0``, and any modification due to ``from __future__ import`` is
discarded. ::
struct PyCompilerFlags {
int cf_flags;
}
2012-01-14 11:42:02 -04:00
.. c:var:: int CO_FUTURE_DIVISION
2007-08-15 11:28:01 -03:00
This bit can be set in *flags* to cause division operator ``/`` to be
interpreted as "true division" according to :pep:`238`.