blob: 62281aabd14430039d69094cec116e730b1051af [file] [log] [blame]
Georg Brandl116aa622007-08-15 14:28:22 +00001.. highlightlang:: c
2
3
4.. _veryhigh:
5
6*************************
7The Very High Level Layer
8*************************
9
10The functions in this chapter will let you execute Python source code given in a
11file or a buffer, but they will not let you interact in a more detailed way with
12the interpreter.
13
14Several of these functions accept a start symbol from the grammar as a
15parameter. The available start symbols are :const:`Py_eval_input`,
16:const:`Py_file_input`, and :const:`Py_single_input`. These are described
17following the functions which accept them as parameters.
18
Benjamin Petersonad3d5c22009-02-26 03:38:59 +000019Note also that several of these functions take :ctype:`FILE\*` parameters. One
Georg Brandl116aa622007-08-15 14:28:22 +000020particular issue which needs to be handled carefully is that the :ctype:`FILE`
21structure for different C libraries can be different and incompatible. Under
22Windows (at least), it is possible for dynamically linked extensions to actually
23use different libraries, so care should be taken that :ctype:`FILE\*` parameters
24are only passed to these functions if it is certain that they were created by
25the same library that the Python runtime is using.
26
27
Martin v. Löwis790465f2008-04-05 20:41:37 +000028.. cfunction:: int Py_Main(int argc, wchar_t **argv)
Georg Brandl116aa622007-08-15 14:28:22 +000029
Martin v. Löwis790465f2008-04-05 20:41:37 +000030 The main program for the standard interpreter. This is made
31 available for programs which embed Python. The *argc* and *argv*
32 parameters should be prepared exactly as those which are passed to
33 a C program's :cfunc:`main` function (converted to wchar_t
34 according to the user's locale). It is important to note that the
35 argument list may be modified (but the contents of the strings
36 pointed to by the argument list are not). The return value will be
37 the integer passed to the :func:`sys.exit` function, ``1`` if the
38 interpreter exits due to an exception, or ``2`` if the parameter
39 list does not represent a valid Python command line.
Georg Brandl116aa622007-08-15 14:28:22 +000040
41
42.. cfunction:: int PyRun_AnyFile(FILE *fp, const char *filename)
43
44 This is a simplified interface to :cfunc:`PyRun_AnyFileExFlags` below, leaving
45 *closeit* set to ``0`` and *flags* set to *NULL*.
46
47
48.. cfunction:: int PyRun_AnyFileFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
49
50 This is a simplified interface to :cfunc:`PyRun_AnyFileExFlags` below, leaving
51 the *closeit* argument set to ``0``.
52
53
54.. cfunction:: int PyRun_AnyFileEx(FILE *fp, const char *filename, int closeit)
55
56 This is a simplified interface to :cfunc:`PyRun_AnyFileExFlags` below, leaving
57 the *flags* argument set to *NULL*.
58
59
60.. cfunction:: int PyRun_AnyFileExFlags(FILE *fp, const char *filename, int closeit, PyCompilerFlags *flags)
61
62 If *fp* refers to a file associated with an interactive device (console or
63 terminal input or Unix pseudo-terminal), return the value of
64 :cfunc:`PyRun_InteractiveLoop`, otherwise return the result of
65 :cfunc:`PyRun_SimpleFile`. If *filename* is *NULL*, this function uses
66 ``"???"`` as the filename.
67
68
69.. cfunction:: int PyRun_SimpleString(const char *command)
70
71 This is a simplified interface to :cfunc:`PyRun_SimpleStringFlags` below,
72 leaving the *PyCompilerFlags\** argument set to NULL.
73
74
75.. cfunction:: int PyRun_SimpleStringFlags(const char *command, PyCompilerFlags *flags)
76
77 Executes the Python source code from *command* in the :mod:`__main__` module
78 according to the *flags* argument. If :mod:`__main__` does not already exist, it
79 is created. Returns ``0`` on success or ``-1`` if an exception was raised. If
80 there was an error, there is no way to get the exception information. For the
81 meaning of *flags*, see below.
82
83
84.. cfunction:: int PyRun_SimpleFile(FILE *fp, const char *filename)
85
86 This is a simplified interface to :cfunc:`PyRun_SimpleFileExFlags` below,
87 leaving *closeit* set to ``0`` and *flags* set to *NULL*.
88
89
90.. cfunction:: int PyRun_SimpleFileFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
91
92 This is a simplified interface to :cfunc:`PyRun_SimpleFileExFlags` below,
93 leaving *closeit* set to ``0``.
94
95
96.. cfunction:: int PyRun_SimpleFileEx(FILE *fp, const char *filename, int closeit)
97
98 This is a simplified interface to :cfunc:`PyRun_SimpleFileExFlags` below,
99 leaving *flags* set to *NULL*.
100
101
102.. cfunction:: int PyRun_SimpleFileExFlags(FILE *fp, const char *filename, int closeit, PyCompilerFlags *flags)
103
104 Similar to :cfunc:`PyRun_SimpleStringFlags`, but the Python source code is read
105 from *fp* instead of an in-memory string. *filename* should be the name of the
106 file. If *closeit* is true, the file is closed before PyRun_SimpleFileExFlags
107 returns.
108
109
110.. cfunction:: int PyRun_InteractiveOne(FILE *fp, const char *filename)
111
112 This is a simplified interface to :cfunc:`PyRun_InteractiveOneFlags` below,
113 leaving *flags* set to *NULL*.
114
115
116.. cfunction:: int PyRun_InteractiveOneFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
117
118 Read and execute a single statement from a file associated with an interactive
119 device according to the *flags* argument. If *filename* is *NULL*, ``"???"`` is
120 used instead. The user will be prompted using ``sys.ps1`` and ``sys.ps2``.
121 Returns ``0`` when the input was executed successfully, ``-1`` if there was an
122 exception, or an error code from the :file:`errcode.h` include file distributed
123 as part of Python if there was a parse error. (Note that :file:`errcode.h` is
124 not included by :file:`Python.h`, so must be included specifically if needed.)
125
126
127.. cfunction:: int PyRun_InteractiveLoop(FILE *fp, const char *filename)
128
129 This is a simplified interface to :cfunc:`PyRun_InteractiveLoopFlags` below,
130 leaving *flags* set to *NULL*.
131
132
133.. cfunction:: int PyRun_InteractiveLoopFlags(FILE *fp, const char *filename, PyCompilerFlags *flags)
134
135 Read and execute statements from a file associated with an interactive device
136 until EOF is reached. If *filename* is *NULL*, ``"???"`` is used instead. The
137 user will be prompted using ``sys.ps1`` and ``sys.ps2``. Returns ``0`` at EOF.
138
139
140.. cfunction:: struct _node* PyParser_SimpleParseString(const char *str, int start)
141
142 This is a simplified interface to
143 :cfunc:`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set
144 to *NULL* and *flags* set to ``0``.
145
146
147.. cfunction:: struct _node* PyParser_SimpleParseStringFlags( const char *str, int start, int flags)
148
149 This is a simplified interface to
150 :cfunc:`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set
151 to *NULL*.
152
153
154.. cfunction:: struct _node* PyParser_SimpleParseStringFlagsFilename( const char *str, const char *filename, int start, int flags)
155
156 Parse Python source code from *str* using the start token *start* according to
157 the *flags* argument. The result can be used to create a code object which can
158 be evaluated efficiently. This is useful if a code fragment must be evaluated
159 many times.
160
161
162.. cfunction:: struct _node* PyParser_SimpleParseFile(FILE *fp, const char *filename, int start)
163
164 This is a simplified interface to :cfunc:`PyParser_SimpleParseFileFlags` below,
165 leaving *flags* set to ``0``
166
167
168.. cfunction:: struct _node* PyParser_SimpleParseFileFlags(FILE *fp, const char *filename, int start, int flags)
169
170 Similar to :cfunc:`PyParser_SimpleParseStringFlagsFilename`, but the Python
171 source code is read from *fp* instead of an in-memory string.
172
173
174.. cfunction:: PyObject* PyRun_String(const char *str, int start, PyObject *globals, PyObject *locals)
175
176 This is a simplified interface to :cfunc:`PyRun_StringFlags` below, leaving
177 *flags* set to *NULL*.
178
179
180.. cfunction:: PyObject* PyRun_StringFlags(const char *str, int start, PyObject *globals, PyObject *locals, PyCompilerFlags *flags)
181
182 Execute Python source code from *str* in the context specified by the
183 dictionaries *globals* and *locals* with the compiler flags specified by
184 *flags*. The parameter *start* specifies the start token that should be used to
185 parse the source code.
186
187 Returns the result of executing the code as a Python object, or *NULL* if an
188 exception was raised.
189
190
191.. cfunction:: PyObject* PyRun_File(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals)
192
193 This is a simplified interface to :cfunc:`PyRun_FileExFlags` below, leaving
194 *closeit* set to ``0`` and *flags* set to *NULL*.
195
196
197.. cfunction:: PyObject* PyRun_FileEx(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, int closeit)
198
199 This is a simplified interface to :cfunc:`PyRun_FileExFlags` below, leaving
200 *flags* set to *NULL*.
201
202
203.. cfunction:: PyObject* PyRun_FileFlags(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, PyCompilerFlags *flags)
204
205 This is a simplified interface to :cfunc:`PyRun_FileExFlags` below, leaving
206 *closeit* set to ``0``.
207
208
209.. cfunction:: PyObject* PyRun_FileExFlags(FILE *fp, const char *filename, int start, PyObject *globals, PyObject *locals, int closeit, PyCompilerFlags *flags)
210
211 Similar to :cfunc:`PyRun_StringFlags`, but the Python source code is read from
212 *fp* instead of an in-memory string. *filename* should be the name of the file.
213 If *closeit* is true, the file is closed before :cfunc:`PyRun_FileExFlags`
214 returns.
215
216
217.. cfunction:: PyObject* Py_CompileString(const char *str, const char *filename, int start)
218
219 This is a simplified interface to :cfunc:`Py_CompileStringFlags` below, leaving
220 *flags* set to *NULL*.
221
222
223.. cfunction:: PyObject* Py_CompileStringFlags(const char *str, const char *filename, int start, PyCompilerFlags *flags)
224
225 Parse and compile the Python source code in *str*, returning the resulting code
226 object. The start token is given by *start*; this can be used to constrain the
227 code which can be compiled and should be :const:`Py_eval_input`,
228 :const:`Py_file_input`, or :const:`Py_single_input`. The filename specified by
229 *filename* is used to construct the code object and may appear in tracebacks or
230 :exc:`SyntaxError` exception messages. This returns *NULL* if the code cannot
231 be parsed or compiled.
232
233
Christian Heimesd8654cf2007-12-02 15:22:16 +0000234.. cfunction:: PyObject* PyEval_EvalCode(PyCodeObject *co, PyObject *globals, PyObject *locals)
235
236 This is a simplified interface to :cfunc:`PyEval_EvalCodeEx`, with just
237 the code object, and the dictionaries of global and local variables.
238 The other arguments are set to *NULL*.
239
240
241.. cfunction:: PyObject* PyEval_EvalCodeEx(PyCodeObject *co, PyObject *globals, PyObject *locals, PyObject **args, int argcount, PyObject **kws, int kwcount, PyObject **defs, int defcount, PyObject *closure)
242
243 Evaluate a precompiled code object, given a particular environment for its
244 evaluation. This environment consists of dictionaries of global and local
245 variables, arrays of arguments, keywords and defaults, and a closure tuple of
246 cells.
247
248
249.. cfunction:: PyObject* PyEval_EvalFrame(PyFrameObject *f)
250
251 Evaluate an execution frame. This is a simplified interface to
252 PyEval_EvalFrameEx, for backward compatibility.
253
254
255.. cfunction:: PyObject* PyEval_EvalFrameEx(PyFrameObject *f, int throwflag)
256
257 This is the main, unvarnished function of Python interpretation. It is
258 literally 2000 lines long. The code object associated with the execution
259 frame *f* is executed, interpreting bytecode and executing calls as needed.
260 The additional *throwflag* parameter can mostly be ignored - if true, then
261 it causes an exception to immediately be thrown; this is used for the
262 :meth:`throw` methods of generator objects.
263
264
265.. cfunction:: int PyEval_MergeCompilerFlags(PyCompilerFlags *cf)
266
267 This function changes the flags of the current evaluation frame, and returns
268 true on success, false on failure.
269
270
Georg Brandl116aa622007-08-15 14:28:22 +0000271.. cvar:: int Py_eval_input
272
273 .. index:: single: Py_CompileString()
274
275 The start symbol from the Python grammar for isolated expressions; for use with
276 :cfunc:`Py_CompileString`.
277
278
279.. cvar:: int Py_file_input
280
281 .. index:: single: Py_CompileString()
282
283 The start symbol from the Python grammar for sequences of statements as read
284 from a file or other source; for use with :cfunc:`Py_CompileString`. This is
285 the symbol to use when compiling arbitrarily long Python source code.
286
287
288.. cvar:: int Py_single_input
289
290 .. index:: single: Py_CompileString()
291
292 The start symbol from the Python grammar for a single statement; for use with
293 :cfunc:`Py_CompileString`. This is the symbol used for the interactive
294 interpreter loop.
295
296
297.. ctype:: struct PyCompilerFlags
298
299 This is the structure used to hold compiler flags. In cases where code is only
300 being compiled, it is passed as ``int flags``, and in cases where code is being
301 executed, it is passed as ``PyCompilerFlags *flags``. In this case, ``from
302 __future__ import`` can modify *flags*.
303
304 Whenever ``PyCompilerFlags *flags`` is *NULL*, :attr:`cf_flags` is treated as
305 equal to ``0``, and any modification due to ``from __future__ import`` is
306 discarded. ::
307
308 struct PyCompilerFlags {
309 int cf_flags;
310 }
311
312
313.. cvar:: int CO_FUTURE_DIVISION
314
315 This bit can be set in *flags* to cause division operator ``/`` to be
316 interpreted as "true division" according to :pep:`238`.
317