Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 1 | .. highlightlang:: c |
| 2 | |
| 3 | |
| 4 | .. _initialization: |
| 5 | |
| 6 | ***************************************** |
| 7 | Initialization, Finalization, and Threads |
| 8 | ***************************************** |
| 9 | |
| 10 | |
| 11 | .. cfunction:: void Py_Initialize() |
| 12 | |
| 13 | .. index:: |
| 14 | single: Py_SetProgramName() |
| 15 | single: PyEval_InitThreads() |
| 16 | single: PyEval_ReleaseLock() |
| 17 | single: PyEval_AcquireLock() |
| 18 | single: modules (in module sys) |
| 19 | single: path (in module sys) |
Georg Brandl | 1a3284e | 2007-12-02 09:40:06 +0000 | [diff] [blame] | 20 | module: builtins |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 21 | module: __main__ |
| 22 | module: sys |
| 23 | triple: module; search; path |
| 24 | single: PySys_SetArgv() |
| 25 | single: Py_Finalize() |
| 26 | |
| 27 | Initialize the Python interpreter. In an application embedding Python, this |
| 28 | should be called before using any other Python/C API functions; with the |
| 29 | exception of :cfunc:`Py_SetProgramName`, :cfunc:`PyEval_InitThreads`, |
| 30 | :cfunc:`PyEval_ReleaseLock`, and :cfunc:`PyEval_AcquireLock`. This initializes |
| 31 | the table of loaded modules (``sys.modules``), and creates the fundamental |
Georg Brandl | 1a3284e | 2007-12-02 09:40:06 +0000 | [diff] [blame] | 32 | modules :mod:`builtins`, :mod:`__main__` and :mod:`sys`. It also initializes |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 33 | the module search path (``sys.path``). It does not set ``sys.argv``; use |
| 34 | :cfunc:`PySys_SetArgv` for that. This is a no-op when called for a second time |
| 35 | (without calling :cfunc:`Py_Finalize` first). There is no return value; it is a |
| 36 | fatal error if the initialization fails. |
| 37 | |
| 38 | |
| 39 | .. cfunction:: void Py_InitializeEx(int initsigs) |
| 40 | |
| 41 | This function works like :cfunc:`Py_Initialize` if *initsigs* is 1. If |
| 42 | *initsigs* is 0, it skips initialization registration of signal handlers, which |
| 43 | might be useful when Python is embedded. |
| 44 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 45 | |
| 46 | .. cfunction:: int Py_IsInitialized() |
| 47 | |
| 48 | Return true (nonzero) when the Python interpreter has been initialized, false |
| 49 | (zero) if not. After :cfunc:`Py_Finalize` is called, this returns false until |
| 50 | :cfunc:`Py_Initialize` is called again. |
| 51 | |
| 52 | |
| 53 | .. cfunction:: void Py_Finalize() |
| 54 | |
| 55 | Undo all initializations made by :cfunc:`Py_Initialize` and subsequent use of |
| 56 | Python/C API functions, and destroy all sub-interpreters (see |
| 57 | :cfunc:`Py_NewInterpreter` below) that were created and not yet destroyed since |
| 58 | the last call to :cfunc:`Py_Initialize`. Ideally, this frees all memory |
| 59 | allocated by the Python interpreter. This is a no-op when called for a second |
| 60 | time (without calling :cfunc:`Py_Initialize` again first). There is no return |
| 61 | value; errors during finalization are ignored. |
| 62 | |
| 63 | This function is provided for a number of reasons. An embedding application |
| 64 | might want to restart Python without having to restart the application itself. |
| 65 | An application that has loaded the Python interpreter from a dynamically |
| 66 | loadable library (or DLL) might want to free all memory allocated by Python |
| 67 | before unloading the DLL. During a hunt for memory leaks in an application a |
| 68 | developer might want to free all memory allocated by Python before exiting from |
| 69 | the application. |
| 70 | |
| 71 | **Bugs and caveats:** The destruction of modules and objects in modules is done |
| 72 | in random order; this may cause destructors (:meth:`__del__` methods) to fail |
| 73 | when they depend on other objects (even functions) or modules. Dynamically |
| 74 | loaded extension modules loaded by Python are not unloaded. Small amounts of |
| 75 | memory allocated by the Python interpreter may not be freed (if you find a leak, |
| 76 | please report it). Memory tied up in circular references between objects is not |
| 77 | freed. Some memory allocated by extension modules may not be freed. Some |
| 78 | extensions may not work properly if their initialization routine is called more |
| 79 | than once; this can happen if an application calls :cfunc:`Py_Initialize` and |
| 80 | :cfunc:`Py_Finalize` more than once. |
| 81 | |
| 82 | |
| 83 | .. cfunction:: PyThreadState* Py_NewInterpreter() |
| 84 | |
| 85 | .. index:: |
Georg Brandl | 1a3284e | 2007-12-02 09:40:06 +0000 | [diff] [blame] | 86 | module: builtins |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 87 | module: __main__ |
| 88 | module: sys |
| 89 | single: stdout (in module sys) |
| 90 | single: stderr (in module sys) |
| 91 | single: stdin (in module sys) |
| 92 | |
| 93 | Create a new sub-interpreter. This is an (almost) totally separate environment |
| 94 | for the execution of Python code. In particular, the new interpreter has |
| 95 | separate, independent versions of all imported modules, including the |
Georg Brandl | 1a3284e | 2007-12-02 09:40:06 +0000 | [diff] [blame] | 96 | fundamental modules :mod:`builtins`, :mod:`__main__` and :mod:`sys`. The |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 97 | table of loaded modules (``sys.modules``) and the module search path |
| 98 | (``sys.path``) are also separate. The new environment has no ``sys.argv`` |
| 99 | variable. It has new standard I/O stream file objects ``sys.stdin``, |
| 100 | ``sys.stdout`` and ``sys.stderr`` (however these refer to the same underlying |
| 101 | :ctype:`FILE` structures in the C library). |
| 102 | |
| 103 | The return value points to the first thread state created in the new |
| 104 | sub-interpreter. This thread state is made in the current thread state. |
| 105 | Note that no actual thread is created; see the discussion of thread states |
| 106 | below. If creation of the new interpreter is unsuccessful, *NULL* is |
| 107 | returned; no exception is set since the exception state is stored in the |
| 108 | current thread state and there may not be a current thread state. (Like all |
| 109 | other Python/C API functions, the global interpreter lock must be held before |
| 110 | calling this function and is still held when it returns; however, unlike most |
| 111 | other Python/C API functions, there needn't be a current thread state on |
| 112 | entry.) |
| 113 | |
| 114 | .. index:: |
| 115 | single: Py_Finalize() |
| 116 | single: Py_Initialize() |
| 117 | |
| 118 | Extension modules are shared between (sub-)interpreters as follows: the first |
| 119 | time a particular extension is imported, it is initialized normally, and a |
| 120 | (shallow) copy of its module's dictionary is squirreled away. When the same |
| 121 | extension is imported by another (sub-)interpreter, a new module is initialized |
| 122 | and filled with the contents of this copy; the extension's ``init`` function is |
| 123 | not called. Note that this is different from what happens when an extension is |
| 124 | imported after the interpreter has been completely re-initialized by calling |
| 125 | :cfunc:`Py_Finalize` and :cfunc:`Py_Initialize`; in that case, the extension's |
| 126 | ``initmodule`` function *is* called again. |
| 127 | |
| 128 | .. index:: single: close() (in module os) |
| 129 | |
| 130 | **Bugs and caveats:** Because sub-interpreters (and the main interpreter) are |
| 131 | part of the same process, the insulation between them isn't perfect --- for |
| 132 | example, using low-level file operations like :func:`os.close` they can |
| 133 | (accidentally or maliciously) affect each other's open files. Because of the |
| 134 | way extensions are shared between (sub-)interpreters, some extensions may not |
| 135 | work properly; this is especially likely when the extension makes use of |
| 136 | (static) global variables, or when the extension manipulates its module's |
| 137 | dictionary after its initialization. It is possible to insert objects created |
| 138 | in one sub-interpreter into a namespace of another sub-interpreter; this should |
| 139 | be done with great care to avoid sharing user-defined functions, methods, |
| 140 | instances or classes between sub-interpreters, since import operations executed |
| 141 | by such objects may affect the wrong (sub-)interpreter's dictionary of loaded |
| 142 | modules. (XXX This is a hard-to-fix bug that will be addressed in a future |
| 143 | release.) |
| 144 | |
| 145 | Also note that the use of this functionality is incompatible with extension |
| 146 | modules such as PyObjC and ctypes that use the :cfunc:`PyGILState_\*` APIs (and |
| 147 | this is inherent in the way the :cfunc:`PyGILState_\*` functions work). Simple |
| 148 | things may work, but confusing behavior will always be near. |
| 149 | |
| 150 | |
| 151 | .. cfunction:: void Py_EndInterpreter(PyThreadState *tstate) |
| 152 | |
| 153 | .. index:: single: Py_Finalize() |
| 154 | |
| 155 | Destroy the (sub-)interpreter represented by the given thread state. The given |
| 156 | thread state must be the current thread state. See the discussion of thread |
| 157 | states below. When the call returns, the current thread state is *NULL*. All |
| 158 | thread states associated with this interpreter are destroyed. (The global |
| 159 | interpreter lock must be held before calling this function and is still held |
| 160 | when it returns.) :cfunc:`Py_Finalize` will destroy all sub-interpreters that |
| 161 | haven't been explicitly destroyed at that point. |
| 162 | |
| 163 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 164 | .. cfunction:: void Py_SetProgramName(wchar_t *name) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 165 | |
| 166 | .. index:: |
| 167 | single: Py_Initialize() |
| 168 | single: main() |
| 169 | single: Py_GetPath() |
| 170 | |
| 171 | This function should be called before :cfunc:`Py_Initialize` is called for |
| 172 | the first time, if it is called at all. It tells the interpreter the value |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 173 | of the ``argv[0]`` argument to the :cfunc:`main` function of the program |
| 174 | (converted to wide characters). |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 175 | This is used by :cfunc:`Py_GetPath` and some other functions below to find |
| 176 | the Python run-time libraries relative to the interpreter executable. The |
| 177 | default value is ``'python'``. The argument should point to a |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 178 | zero-terminated wide character string in static storage whose contents will not |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 179 | change for the duration of the program's execution. No code in the Python |
| 180 | interpreter will change the contents of this storage. |
| 181 | |
| 182 | |
| 183 | .. cfunction:: char* Py_GetProgramName() |
| 184 | |
| 185 | .. index:: single: Py_SetProgramName() |
| 186 | |
| 187 | Return the program name set with :cfunc:`Py_SetProgramName`, or the default. |
| 188 | The returned string points into static storage; the caller should not modify its |
| 189 | value. |
| 190 | |
| 191 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 192 | .. cfunction:: wchar_t* Py_GetPrefix() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 193 | |
| 194 | Return the *prefix* for installed platform-independent files. This is derived |
| 195 | through a number of complicated rules from the program name set with |
| 196 | :cfunc:`Py_SetProgramName` and some environment variables; for example, if the |
| 197 | program name is ``'/usr/local/bin/python'``, the prefix is ``'/usr/local'``. The |
| 198 | returned string points into static storage; the caller should not modify its |
| 199 | value. This corresponds to the :makevar:`prefix` variable in the top-level |
| 200 | :file:`Makefile` and the :option:`--prefix` argument to the :program:`configure` |
| 201 | script at build time. The value is available to Python code as ``sys.prefix``. |
| 202 | It is only useful on Unix. See also the next function. |
| 203 | |
| 204 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 205 | .. cfunction:: wchar_t* Py_GetExecPrefix() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 206 | |
| 207 | Return the *exec-prefix* for installed platform-*dependent* files. This is |
| 208 | derived through a number of complicated rules from the program name set with |
| 209 | :cfunc:`Py_SetProgramName` and some environment variables; for example, if the |
| 210 | program name is ``'/usr/local/bin/python'``, the exec-prefix is |
| 211 | ``'/usr/local'``. The returned string points into static storage; the caller |
| 212 | should not modify its value. This corresponds to the :makevar:`exec_prefix` |
| 213 | variable in the top-level :file:`Makefile` and the :option:`--exec-prefix` |
| 214 | argument to the :program:`configure` script at build time. The value is |
| 215 | available to Python code as ``sys.exec_prefix``. It is only useful on Unix. |
| 216 | |
| 217 | Background: The exec-prefix differs from the prefix when platform dependent |
| 218 | files (such as executables and shared libraries) are installed in a different |
| 219 | directory tree. In a typical installation, platform dependent files may be |
| 220 | installed in the :file:`/usr/local/plat` subtree while platform independent may |
| 221 | be installed in :file:`/usr/local`. |
| 222 | |
| 223 | Generally speaking, a platform is a combination of hardware and software |
| 224 | families, e.g. Sparc machines running the Solaris 2.x operating system are |
| 225 | considered the same platform, but Intel machines running Solaris 2.x are another |
| 226 | platform, and Intel machines running Linux are yet another platform. Different |
| 227 | major revisions of the same operating system generally also form different |
| 228 | platforms. Non-Unix operating systems are a different story; the installation |
| 229 | strategies on those systems are so different that the prefix and exec-prefix are |
| 230 | meaningless, and set to the empty string. Note that compiled Python bytecode |
| 231 | files are platform independent (but not independent from the Python version by |
| 232 | which they were compiled!). |
| 233 | |
| 234 | System administrators will know how to configure the :program:`mount` or |
| 235 | :program:`automount` programs to share :file:`/usr/local` between platforms |
| 236 | while having :file:`/usr/local/plat` be a different filesystem for each |
| 237 | platform. |
| 238 | |
| 239 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 240 | .. cfunction:: wchar_t* Py_GetProgramFullPath() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 241 | |
| 242 | .. index:: |
| 243 | single: Py_SetProgramName() |
| 244 | single: executable (in module sys) |
| 245 | |
| 246 | Return the full program name of the Python executable; this is computed as a |
| 247 | side-effect of deriving the default module search path from the program name |
| 248 | (set by :cfunc:`Py_SetProgramName` above). The returned string points into |
| 249 | static storage; the caller should not modify its value. The value is available |
| 250 | to Python code as ``sys.executable``. |
| 251 | |
| 252 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 253 | .. cfunction:: wchar_t* Py_GetPath() |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 254 | |
| 255 | .. index:: |
| 256 | triple: module; search; path |
| 257 | single: path (in module sys) |
| 258 | |
| 259 | Return the default module search path; this is computed from the program name |
| 260 | (set by :cfunc:`Py_SetProgramName` above) and some environment variables. The |
| 261 | returned string consists of a series of directory names separated by a platform |
| 262 | dependent delimiter character. The delimiter character is ``':'`` on Unix and |
| 263 | Mac OS X, ``';'`` on Windows. The returned string points into static storage; |
| 264 | the caller should not modify its value. The value is available to Python code |
| 265 | as the list ``sys.path``, which may be modified to change the future search path |
| 266 | for loaded modules. |
| 267 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 268 | .. XXX should give the exact rules |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 269 | |
| 270 | |
| 271 | .. cfunction:: const char* Py_GetVersion() |
| 272 | |
| 273 | Return the version of this Python interpreter. This is a string that looks |
| 274 | something like :: |
| 275 | |
Georg Brandl | e6bcc91 | 2008-05-12 18:05:20 +0000 | [diff] [blame] | 276 | "3.0a5+ (py3k:63103M, May 12 2008, 00:53:55) \n[GCC 4.2.3]" |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 277 | |
| 278 | .. index:: single: version (in module sys) |
| 279 | |
| 280 | The first word (up to the first space character) is the current Python version; |
| 281 | the first three characters are the major and minor version separated by a |
| 282 | period. The returned string points into static storage; the caller should not |
Georg Brandl | e6bcc91 | 2008-05-12 18:05:20 +0000 | [diff] [blame] | 283 | modify its value. The value is available to Python code as :data:`sys.version`. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 284 | |
| 285 | |
| 286 | .. cfunction:: const char* Py_GetBuildNumber() |
| 287 | |
| 288 | Return a string representing the Subversion revision that this Python executable |
| 289 | was built from. This number is a string because it may contain a trailing 'M' |
| 290 | if Python was built from a mixed revision source tree. |
| 291 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 292 | |
| 293 | .. cfunction:: const char* Py_GetPlatform() |
| 294 | |
| 295 | .. index:: single: platform (in module sys) |
| 296 | |
| 297 | Return the platform identifier for the current platform. On Unix, this is |
| 298 | formed from the "official" name of the operating system, converted to lower |
| 299 | case, followed by the major revision number; e.g., for Solaris 2.x, which is |
| 300 | also known as SunOS 5.x, the value is ``'sunos5'``. On Mac OS X, it is |
| 301 | ``'darwin'``. On Windows, it is ``'win'``. The returned string points into |
| 302 | static storage; the caller should not modify its value. The value is available |
| 303 | to Python code as ``sys.platform``. |
| 304 | |
| 305 | |
| 306 | .. cfunction:: const char* Py_GetCopyright() |
| 307 | |
| 308 | Return the official copyright string for the current Python version, for example |
| 309 | |
| 310 | ``'Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam'`` |
| 311 | |
| 312 | .. index:: single: copyright (in module sys) |
| 313 | |
| 314 | The returned string points into static storage; the caller should not modify its |
| 315 | value. The value is available to Python code as ``sys.copyright``. |
| 316 | |
| 317 | |
| 318 | .. cfunction:: const char* Py_GetCompiler() |
| 319 | |
| 320 | Return an indication of the compiler used to build the current Python version, |
| 321 | in square brackets, for example:: |
| 322 | |
| 323 | "[GCC 2.7.2.2]" |
| 324 | |
| 325 | .. index:: single: version (in module sys) |
| 326 | |
| 327 | The returned string points into static storage; the caller should not modify its |
| 328 | value. The value is available to Python code as part of the variable |
| 329 | ``sys.version``. |
| 330 | |
| 331 | |
| 332 | .. cfunction:: const char* Py_GetBuildInfo() |
| 333 | |
| 334 | Return information about the sequence number and build date and time of the |
| 335 | current Python interpreter instance, for example :: |
| 336 | |
| 337 | "#67, Aug 1 1997, 22:34:28" |
| 338 | |
| 339 | .. index:: single: version (in module sys) |
| 340 | |
| 341 | The returned string points into static storage; the caller should not modify its |
| 342 | value. The value is available to Python code as part of the variable |
| 343 | ``sys.version``. |
| 344 | |
| 345 | |
Martin v. Löwis | 790465f | 2008-04-05 20:41:37 +0000 | [diff] [blame] | 346 | .. cfunction:: void PySys_SetArgv(int argc, wchar_t **argv) |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 347 | |
| 348 | .. index:: |
| 349 | single: main() |
| 350 | single: Py_FatalError() |
| 351 | single: argv (in module sys) |
| 352 | |
| 353 | Set ``sys.argv`` based on *argc* and *argv*. These parameters are similar to |
| 354 | those passed to the program's :cfunc:`main` function with the difference that |
| 355 | the first entry should refer to the script file to be executed rather than the |
| 356 | executable hosting the Python interpreter. If there isn't a script that will be |
| 357 | run, the first entry in *argv* can be an empty string. If this function fails |
| 358 | to initialize ``sys.argv``, a fatal condition is signalled using |
| 359 | :cfunc:`Py_FatalError`. |
| 360 | |
Christian Heimes | 5b5e81c | 2007-12-31 16:14:33 +0000 | [diff] [blame] | 361 | .. XXX impl. doesn't seem consistent in allowing 0/NULL for the params; |
| 362 | check w/ Guido. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 363 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 364 | |
| 365 | .. _threads: |
| 366 | |
| 367 | Thread State and the Global Interpreter Lock |
| 368 | ============================================ |
| 369 | |
| 370 | .. index:: |
| 371 | single: global interpreter lock |
| 372 | single: interpreter lock |
| 373 | single: lock, interpreter |
| 374 | |
| 375 | The Python interpreter is not fully thread safe. In order to support |
| 376 | multi-threaded Python programs, there's a global lock that must be held by the |
| 377 | current thread before it can safely access Python objects. Without the lock, |
| 378 | even the simplest operations could cause problems in a multi-threaded program: |
| 379 | for example, when two threads simultaneously increment the reference count of |
| 380 | the same object, the reference count could end up being incremented only once |
| 381 | instead of twice. |
| 382 | |
| 383 | .. index:: single: setcheckinterval() (in module sys) |
| 384 | |
| 385 | Therefore, the rule exists that only the thread that has acquired the global |
| 386 | interpreter lock may operate on Python objects or call Python/C API functions. |
| 387 | In order to support multi-threaded Python programs, the interpreter regularly |
| 388 | releases and reacquires the lock --- by default, every 100 bytecode instructions |
| 389 | (this can be changed with :func:`sys.setcheckinterval`). The lock is also |
| 390 | released and reacquired around potentially blocking I/O operations like reading |
| 391 | or writing a file, so that other threads can run while the thread that requests |
| 392 | the I/O is waiting for the I/O operation to complete. |
| 393 | |
| 394 | .. index:: |
| 395 | single: PyThreadState |
| 396 | single: PyThreadState |
| 397 | |
| 398 | The Python interpreter needs to keep some bookkeeping information separate per |
| 399 | thread --- for this it uses a data structure called :ctype:`PyThreadState`. |
| 400 | There's one global variable, however: the pointer to the current |
| 401 | :ctype:`PyThreadState` structure. While most thread packages have a way to |
| 402 | store "per-thread global data," Python's internal platform independent thread |
| 403 | abstraction doesn't support this yet. Therefore, the current thread state must |
| 404 | be manipulated explicitly. |
| 405 | |
| 406 | This is easy enough in most cases. Most code manipulating the global |
| 407 | interpreter lock has the following simple structure:: |
| 408 | |
| 409 | Save the thread state in a local variable. |
| 410 | Release the interpreter lock. |
| 411 | ...Do some blocking I/O operation... |
| 412 | Reacquire the interpreter lock. |
| 413 | Restore the thread state from the local variable. |
| 414 | |
| 415 | This is so common that a pair of macros exists to simplify it:: |
| 416 | |
| 417 | Py_BEGIN_ALLOW_THREADS |
| 418 | ...Do some blocking I/O operation... |
| 419 | Py_END_ALLOW_THREADS |
| 420 | |
| 421 | .. index:: |
| 422 | single: Py_BEGIN_ALLOW_THREADS |
| 423 | single: Py_END_ALLOW_THREADS |
| 424 | |
| 425 | The :cmacro:`Py_BEGIN_ALLOW_THREADS` macro opens a new block and declares a |
| 426 | hidden local variable; the :cmacro:`Py_END_ALLOW_THREADS` macro closes the |
| 427 | block. Another advantage of using these two macros is that when Python is |
| 428 | compiled without thread support, they are defined empty, thus saving the thread |
| 429 | state and lock manipulations. |
| 430 | |
| 431 | When thread support is enabled, the block above expands to the following code:: |
| 432 | |
| 433 | PyThreadState *_save; |
| 434 | |
| 435 | _save = PyEval_SaveThread(); |
| 436 | ...Do some blocking I/O operation... |
| 437 | PyEval_RestoreThread(_save); |
| 438 | |
| 439 | Using even lower level primitives, we can get roughly the same effect as |
| 440 | follows:: |
| 441 | |
| 442 | PyThreadState *_save; |
| 443 | |
| 444 | _save = PyThreadState_Swap(NULL); |
| 445 | PyEval_ReleaseLock(); |
| 446 | ...Do some blocking I/O operation... |
| 447 | PyEval_AcquireLock(); |
| 448 | PyThreadState_Swap(_save); |
| 449 | |
| 450 | .. index:: |
| 451 | single: PyEval_RestoreThread() |
| 452 | single: errno |
| 453 | single: PyEval_SaveThread() |
| 454 | single: PyEval_ReleaseLock() |
| 455 | single: PyEval_AcquireLock() |
| 456 | |
| 457 | There are some subtle differences; in particular, :cfunc:`PyEval_RestoreThread` |
| 458 | saves and restores the value of the global variable :cdata:`errno`, since the |
| 459 | lock manipulation does not guarantee that :cdata:`errno` is left alone. Also, |
| 460 | when thread support is disabled, :cfunc:`PyEval_SaveThread` and |
| 461 | :cfunc:`PyEval_RestoreThread` don't manipulate the lock; in this case, |
| 462 | :cfunc:`PyEval_ReleaseLock` and :cfunc:`PyEval_AcquireLock` are not available. |
| 463 | This is done so that dynamically loaded extensions compiled with thread support |
| 464 | enabled can be loaded by an interpreter that was compiled with disabled thread |
| 465 | support. |
| 466 | |
| 467 | The global interpreter lock is used to protect the pointer to the current thread |
| 468 | state. When releasing the lock and saving the thread state, the current thread |
| 469 | state pointer must be retrieved before the lock is released (since another |
| 470 | thread could immediately acquire the lock and store its own thread state in the |
| 471 | global variable). Conversely, when acquiring the lock and restoring the thread |
| 472 | state, the lock must be acquired before storing the thread state pointer. |
| 473 | |
| 474 | Why am I going on with so much detail about this? Because when threads are |
| 475 | created from C, they don't have the global interpreter lock, nor is there a |
| 476 | thread state data structure for them. Such threads must bootstrap themselves |
| 477 | into existence, by first creating a thread state data structure, then acquiring |
| 478 | the lock, and finally storing their thread state pointer, before they can start |
| 479 | using the Python/C API. When they are done, they should reset the thread state |
| 480 | pointer, release the lock, and finally free their thread state data structure. |
| 481 | |
Georg Brandl | e6bcc91 | 2008-05-12 18:05:20 +0000 | [diff] [blame] | 482 | Threads can take advantage of the :cfunc:`PyGILState_\*` functions to do all of |
| 483 | the above automatically. The typical idiom for calling into Python from a C |
| 484 | thread is now:: |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 485 | |
| 486 | PyGILState_STATE gstate; |
| 487 | gstate = PyGILState_Ensure(); |
| 488 | |
| 489 | /* Perform Python actions here. */ |
| 490 | result = CallSomeFunction(); |
| 491 | /* evaluate result */ |
| 492 | |
| 493 | /* Release the thread. No Python API allowed beyond this point. */ |
| 494 | PyGILState_Release(gstate); |
| 495 | |
| 496 | Note that the :cfunc:`PyGILState_\*` functions assume there is only one global |
| 497 | interpreter (created automatically by :cfunc:`Py_Initialize`). Python still |
| 498 | supports the creation of additional interpreters (using |
| 499 | :cfunc:`Py_NewInterpreter`), but mixing multiple interpreters and the |
| 500 | :cfunc:`PyGILState_\*` API is unsupported. |
| 501 | |
| 502 | |
| 503 | .. ctype:: PyInterpreterState |
| 504 | |
| 505 | This data structure represents the state shared by a number of cooperating |
| 506 | threads. Threads belonging to the same interpreter share their module |
| 507 | administration and a few other internal items. There are no public members in |
| 508 | this structure. |
| 509 | |
| 510 | Threads belonging to different interpreters initially share nothing, except |
| 511 | process state like available memory, open file descriptors and such. The global |
| 512 | interpreter lock is also shared by all threads, regardless of to which |
| 513 | interpreter they belong. |
| 514 | |
| 515 | |
| 516 | .. ctype:: PyThreadState |
| 517 | |
| 518 | This data structure represents the state of a single thread. The only public |
| 519 | data member is :ctype:`PyInterpreterState \*`:attr:`interp`, which points to |
| 520 | this thread's interpreter state. |
| 521 | |
| 522 | |
| 523 | .. cfunction:: void PyEval_InitThreads() |
| 524 | |
| 525 | .. index:: |
| 526 | single: PyEval_ReleaseLock() |
| 527 | single: PyEval_ReleaseThread() |
| 528 | single: PyEval_SaveThread() |
| 529 | single: PyEval_RestoreThread() |
| 530 | |
| 531 | Initialize and acquire the global interpreter lock. It should be called in the |
| 532 | main thread before creating a second thread or engaging in any other thread |
| 533 | operations such as :cfunc:`PyEval_ReleaseLock` or |
| 534 | ``PyEval_ReleaseThread(tstate)``. It is not needed before calling |
| 535 | :cfunc:`PyEval_SaveThread` or :cfunc:`PyEval_RestoreThread`. |
| 536 | |
| 537 | .. index:: single: Py_Initialize() |
| 538 | |
| 539 | This is a no-op when called for a second time. It is safe to call this function |
| 540 | before calling :cfunc:`Py_Initialize`. |
| 541 | |
Georg Brandl | 2067bfd | 2008-05-25 13:05:15 +0000 | [diff] [blame^] | 542 | .. index:: module: _thread |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 543 | |
| 544 | When only the main thread exists, no lock operations are needed. This is a |
| 545 | common situation (most Python programs do not use threads), and the lock |
| 546 | operations slow the interpreter down a bit. Therefore, the lock is not created |
| 547 | initially. This situation is equivalent to having acquired the lock: when |
| 548 | there is only a single thread, all object accesses are safe. Therefore, when |
| 549 | this function initializes the lock, it also acquires it. Before the Python |
Georg Brandl | 2067bfd | 2008-05-25 13:05:15 +0000 | [diff] [blame^] | 550 | :mod:`_thread` module creates a new thread, knowing that either it has the lock |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 551 | or the lock hasn't been created yet, it calls :cfunc:`PyEval_InitThreads`. When |
| 552 | this call returns, it is guaranteed that the lock has been created and that the |
| 553 | calling thread has acquired it. |
| 554 | |
| 555 | It is **not** safe to call this function when it is unknown which thread (if |
| 556 | any) currently has the global interpreter lock. |
| 557 | |
| 558 | This function is not available when thread support is disabled at compile time. |
| 559 | |
| 560 | |
| 561 | .. cfunction:: int PyEval_ThreadsInitialized() |
| 562 | |
| 563 | Returns a non-zero value if :cfunc:`PyEval_InitThreads` has been called. This |
| 564 | function can be called without holding the lock, and therefore can be used to |
| 565 | avoid calls to the locking API when running single-threaded. This function is |
| 566 | not available when thread support is disabled at compile time. |
| 567 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 568 | |
| 569 | .. cfunction:: void PyEval_AcquireLock() |
| 570 | |
| 571 | Acquire the global interpreter lock. The lock must have been created earlier. |
| 572 | If this thread already has the lock, a deadlock ensues. This function is not |
| 573 | available when thread support is disabled at compile time. |
| 574 | |
| 575 | |
| 576 | .. cfunction:: void PyEval_ReleaseLock() |
| 577 | |
| 578 | Release the global interpreter lock. The lock must have been created earlier. |
| 579 | This function is not available when thread support is disabled at compile time. |
| 580 | |
| 581 | |
| 582 | .. cfunction:: void PyEval_AcquireThread(PyThreadState *tstate) |
| 583 | |
| 584 | Acquire the global interpreter lock and set the current thread state to |
| 585 | *tstate*, which should not be *NULL*. The lock must have been created earlier. |
| 586 | If this thread already has the lock, deadlock ensues. This function is not |
| 587 | available when thread support is disabled at compile time. |
| 588 | |
| 589 | |
| 590 | .. cfunction:: void PyEval_ReleaseThread(PyThreadState *tstate) |
| 591 | |
| 592 | Reset the current thread state to *NULL* and release the global interpreter |
| 593 | lock. The lock must have been created earlier and must be held by the current |
| 594 | thread. The *tstate* argument, which must not be *NULL*, is only used to check |
| 595 | that it represents the current thread state --- if it isn't, a fatal error is |
| 596 | reported. This function is not available when thread support is disabled at |
| 597 | compile time. |
| 598 | |
| 599 | |
| 600 | .. cfunction:: PyThreadState* PyEval_SaveThread() |
| 601 | |
| 602 | Release the interpreter lock (if it has been created and thread support is |
| 603 | enabled) and reset the thread state to *NULL*, returning the previous thread |
| 604 | state (which is not *NULL*). If the lock has been created, the current thread |
| 605 | must have acquired it. (This function is available even when thread support is |
| 606 | disabled at compile time.) |
| 607 | |
| 608 | |
| 609 | .. cfunction:: void PyEval_RestoreThread(PyThreadState *tstate) |
| 610 | |
| 611 | Acquire the interpreter lock (if it has been created and thread support is |
| 612 | enabled) and set the thread state to *tstate*, which must not be *NULL*. If the |
| 613 | lock has been created, the current thread must not have acquired it, otherwise |
| 614 | deadlock ensues. (This function is available even when thread support is |
| 615 | disabled at compile time.) |
| 616 | |
Christian Heimes | d8654cf | 2007-12-02 15:22:16 +0000 | [diff] [blame] | 617 | |
| 618 | .. cfunction:: void PyEval_ReInitThreads() |
| 619 | |
| 620 | This function is called from :cfunc:`PyOS_AfterFork` to ensure that newly |
| 621 | created child processes don't hold locks referring to threads which |
| 622 | are not running in the child process. |
| 623 | |
| 624 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 625 | The following macros are normally used without a trailing semicolon; look for |
| 626 | example usage in the Python source distribution. |
| 627 | |
| 628 | |
| 629 | .. cmacro:: Py_BEGIN_ALLOW_THREADS |
| 630 | |
| 631 | This macro expands to ``{ PyThreadState *_save; _save = PyEval_SaveThread();``. |
| 632 | Note that it contains an opening brace; it must be matched with a following |
| 633 | :cmacro:`Py_END_ALLOW_THREADS` macro. See above for further discussion of this |
| 634 | macro. It is a no-op when thread support is disabled at compile time. |
| 635 | |
| 636 | |
| 637 | .. cmacro:: Py_END_ALLOW_THREADS |
| 638 | |
| 639 | This macro expands to ``PyEval_RestoreThread(_save); }``. Note that it contains |
| 640 | a closing brace; it must be matched with an earlier |
| 641 | :cmacro:`Py_BEGIN_ALLOW_THREADS` macro. See above for further discussion of |
| 642 | this macro. It is a no-op when thread support is disabled at compile time. |
| 643 | |
| 644 | |
| 645 | .. cmacro:: Py_BLOCK_THREADS |
| 646 | |
| 647 | This macro expands to ``PyEval_RestoreThread(_save);``: it is equivalent to |
| 648 | :cmacro:`Py_END_ALLOW_THREADS` without the closing brace. It is a no-op when |
| 649 | thread support is disabled at compile time. |
| 650 | |
| 651 | |
| 652 | .. cmacro:: Py_UNBLOCK_THREADS |
| 653 | |
| 654 | This macro expands to ``_save = PyEval_SaveThread();``: it is equivalent to |
| 655 | :cmacro:`Py_BEGIN_ALLOW_THREADS` without the opening brace and variable |
| 656 | declaration. It is a no-op when thread support is disabled at compile time. |
| 657 | |
| 658 | All of the following functions are only available when thread support is enabled |
| 659 | at compile time, and must be called only when the interpreter lock has been |
| 660 | created. |
| 661 | |
| 662 | |
| 663 | .. cfunction:: PyInterpreterState* PyInterpreterState_New() |
| 664 | |
| 665 | Create a new interpreter state object. The interpreter lock need not be held, |
| 666 | but may be held if it is necessary to serialize calls to this function. |
| 667 | |
| 668 | |
| 669 | .. cfunction:: void PyInterpreterState_Clear(PyInterpreterState *interp) |
| 670 | |
| 671 | Reset all information in an interpreter state object. The interpreter lock must |
| 672 | be held. |
| 673 | |
| 674 | |
| 675 | .. cfunction:: void PyInterpreterState_Delete(PyInterpreterState *interp) |
| 676 | |
| 677 | Destroy an interpreter state object. The interpreter lock need not be held. |
| 678 | The interpreter state must have been reset with a previous call to |
| 679 | :cfunc:`PyInterpreterState_Clear`. |
| 680 | |
| 681 | |
| 682 | .. cfunction:: PyThreadState* PyThreadState_New(PyInterpreterState *interp) |
| 683 | |
| 684 | Create a new thread state object belonging to the given interpreter object. The |
| 685 | interpreter lock need not be held, but may be held if it is necessary to |
| 686 | serialize calls to this function. |
| 687 | |
| 688 | |
| 689 | .. cfunction:: void PyThreadState_Clear(PyThreadState *tstate) |
| 690 | |
| 691 | Reset all information in a thread state object. The interpreter lock must be |
| 692 | held. |
| 693 | |
| 694 | |
| 695 | .. cfunction:: void PyThreadState_Delete(PyThreadState *tstate) |
| 696 | |
| 697 | Destroy a thread state object. The interpreter lock need not be held. The |
| 698 | thread state must have been reset with a previous call to |
| 699 | :cfunc:`PyThreadState_Clear`. |
| 700 | |
| 701 | |
| 702 | .. cfunction:: PyThreadState* PyThreadState_Get() |
| 703 | |
| 704 | Return the current thread state. The interpreter lock must be held. When the |
| 705 | current thread state is *NULL*, this issues a fatal error (so that the caller |
| 706 | needn't check for *NULL*). |
| 707 | |
| 708 | |
| 709 | .. cfunction:: PyThreadState* PyThreadState_Swap(PyThreadState *tstate) |
| 710 | |
| 711 | Swap the current thread state with the thread state given by the argument |
| 712 | *tstate*, which may be *NULL*. The interpreter lock must be held. |
| 713 | |
| 714 | |
| 715 | .. cfunction:: PyObject* PyThreadState_GetDict() |
| 716 | |
| 717 | Return a dictionary in which extensions can store thread-specific state |
| 718 | information. Each extension should use a unique key to use to store state in |
| 719 | the dictionary. It is okay to call this function when no current thread state |
| 720 | is available. If this function returns *NULL*, no exception has been raised and |
| 721 | the caller should assume no current thread state is available. |
| 722 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 723 | |
| 724 | .. cfunction:: int PyThreadState_SetAsyncExc(long id, PyObject *exc) |
| 725 | |
| 726 | Asynchronously raise an exception in a thread. The *id* argument is the thread |
| 727 | id of the target thread; *exc* is the exception object to be raised. This |
| 728 | function does not steal any references to *exc*. To prevent naive misuse, you |
| 729 | must write your own C extension to call this. Must be called with the GIL held. |
| 730 | Returns the number of thread states modified; this is normally one, but will be |
| 731 | zero if the thread id isn't found. If *exc* is :const:`NULL`, the pending |
| 732 | exception (if any) for the thread is cleared. This raises no exceptions. |
| 733 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 734 | |
| 735 | .. cfunction:: PyGILState_STATE PyGILState_Ensure() |
| 736 | |
| 737 | Ensure that the current thread is ready to call the Python C API regardless of |
| 738 | the current state of Python, or of its thread lock. This may be called as many |
| 739 | times as desired by a thread as long as each call is matched with a call to |
| 740 | :cfunc:`PyGILState_Release`. In general, other thread-related APIs may be used |
| 741 | between :cfunc:`PyGILState_Ensure` and :cfunc:`PyGILState_Release` calls as long |
| 742 | as the thread state is restored to its previous state before the Release(). For |
| 743 | example, normal usage of the :cmacro:`Py_BEGIN_ALLOW_THREADS` and |
| 744 | :cmacro:`Py_END_ALLOW_THREADS` macros is acceptable. |
| 745 | |
| 746 | The return value is an opaque "handle" to the thread state when |
| 747 | :cfunc:`PyGILState_Acquire` was called, and must be passed to |
| 748 | :cfunc:`PyGILState_Release` to ensure Python is left in the same state. Even |
| 749 | though recursive calls are allowed, these handles *cannot* be shared - each |
| 750 | unique call to :cfunc:`PyGILState_Ensure` must save the handle for its call to |
| 751 | :cfunc:`PyGILState_Release`. |
| 752 | |
| 753 | When the function returns, the current thread will hold the GIL. Failure is a |
| 754 | fatal error. |
| 755 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 756 | |
| 757 | .. cfunction:: void PyGILState_Release(PyGILState_STATE) |
| 758 | |
| 759 | Release any resources previously acquired. After this call, Python's state will |
| 760 | be the same as it was prior to the corresponding :cfunc:`PyGILState_Ensure` call |
| 761 | (but generally this state will be unknown to the caller, hence the use of the |
| 762 | GILState API.) |
| 763 | |
| 764 | Every call to :cfunc:`PyGILState_Ensure` must be matched by a call to |
| 765 | :cfunc:`PyGILState_Release` on the same thread. |
| 766 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 767 | |
| 768 | .. _profiling: |
| 769 | |
| 770 | Profiling and Tracing |
| 771 | ===================== |
| 772 | |
| 773 | .. sectionauthor:: Fred L. Drake, Jr. <fdrake@acm.org> |
| 774 | |
| 775 | |
| 776 | The Python interpreter provides some low-level support for attaching profiling |
| 777 | and execution tracing facilities. These are used for profiling, debugging, and |
| 778 | coverage analysis tools. |
| 779 | |
Georg Brandl | e6bcc91 | 2008-05-12 18:05:20 +0000 | [diff] [blame] | 780 | This C interface allows the profiling or tracing code to avoid the overhead of |
| 781 | calling through Python-level callable objects, making a direct C function call |
| 782 | instead. The essential attributes of the facility have not changed; the |
| 783 | interface allows trace functions to be installed per-thread, and the basic |
| 784 | events reported to the trace function are the same as had been reported to the |
| 785 | Python-level trace functions in previous versions. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 786 | |
| 787 | |
| 788 | .. ctype:: int (*Py_tracefunc)(PyObject *obj, PyFrameObject *frame, int what, PyObject *arg) |
| 789 | |
| 790 | The type of the trace function registered using :cfunc:`PyEval_SetProfile` and |
| 791 | :cfunc:`PyEval_SetTrace`. The first parameter is the object passed to the |
| 792 | registration function as *obj*, *frame* is the frame object to which the event |
| 793 | pertains, *what* is one of the constants :const:`PyTrace_CALL`, |
| 794 | :const:`PyTrace_EXCEPTION`, :const:`PyTrace_LINE`, :const:`PyTrace_RETURN`, |
| 795 | :const:`PyTrace_C_CALL`, :const:`PyTrace_C_EXCEPTION`, or |
| 796 | :const:`PyTrace_C_RETURN`, and *arg* depends on the value of *what*: |
| 797 | |
| 798 | +------------------------------+--------------------------------------+ |
| 799 | | Value of *what* | Meaning of *arg* | |
| 800 | +==============================+======================================+ |
| 801 | | :const:`PyTrace_CALL` | Always *NULL*. | |
| 802 | +------------------------------+--------------------------------------+ |
| 803 | | :const:`PyTrace_EXCEPTION` | Exception information as returned by | |
| 804 | | | :func:`sys.exc_info`. | |
| 805 | +------------------------------+--------------------------------------+ |
| 806 | | :const:`PyTrace_LINE` | Always *NULL*. | |
| 807 | +------------------------------+--------------------------------------+ |
| 808 | | :const:`PyTrace_RETURN` | Value being returned to the caller. | |
| 809 | +------------------------------+--------------------------------------+ |
| 810 | | :const:`PyTrace_C_CALL` | Name of function being called. | |
| 811 | +------------------------------+--------------------------------------+ |
| 812 | | :const:`PyTrace_C_EXCEPTION` | Always *NULL*. | |
| 813 | +------------------------------+--------------------------------------+ |
| 814 | | :const:`PyTrace_C_RETURN` | Always *NULL*. | |
| 815 | +------------------------------+--------------------------------------+ |
| 816 | |
| 817 | |
| 818 | .. cvar:: int PyTrace_CALL |
| 819 | |
| 820 | The value of the *what* parameter to a :ctype:`Py_tracefunc` function when a new |
| 821 | call to a function or method is being reported, or a new entry into a generator. |
| 822 | Note that the creation of the iterator for a generator function is not reported |
| 823 | as there is no control transfer to the Python bytecode in the corresponding |
| 824 | frame. |
| 825 | |
| 826 | |
| 827 | .. cvar:: int PyTrace_EXCEPTION |
| 828 | |
| 829 | The value of the *what* parameter to a :ctype:`Py_tracefunc` function when an |
| 830 | exception has been raised. The callback function is called with this value for |
| 831 | *what* when after any bytecode is processed after which the exception becomes |
| 832 | set within the frame being executed. The effect of this is that as exception |
| 833 | propagation causes the Python stack to unwind, the callback is called upon |
| 834 | return to each frame as the exception propagates. Only trace functions receives |
| 835 | these events; they are not needed by the profiler. |
| 836 | |
| 837 | |
| 838 | .. cvar:: int PyTrace_LINE |
| 839 | |
| 840 | The value passed as the *what* parameter to a trace function (but not a |
| 841 | profiling function) when a line-number event is being reported. |
| 842 | |
| 843 | |
| 844 | .. cvar:: int PyTrace_RETURN |
| 845 | |
| 846 | The value for the *what* parameter to :ctype:`Py_tracefunc` functions when a |
| 847 | call is returning without propagating an exception. |
| 848 | |
| 849 | |
| 850 | .. cvar:: int PyTrace_C_CALL |
| 851 | |
| 852 | The value for the *what* parameter to :ctype:`Py_tracefunc` functions when a C |
| 853 | function is about to be called. |
| 854 | |
| 855 | |
| 856 | .. cvar:: int PyTrace_C_EXCEPTION |
| 857 | |
| 858 | The value for the *what* parameter to :ctype:`Py_tracefunc` functions when a C |
| 859 | function has thrown an exception. |
| 860 | |
| 861 | |
| 862 | .. cvar:: int PyTrace_C_RETURN |
| 863 | |
| 864 | The value for the *what* parameter to :ctype:`Py_tracefunc` functions when a C |
| 865 | function has returned. |
| 866 | |
| 867 | |
| 868 | .. cfunction:: void PyEval_SetProfile(Py_tracefunc func, PyObject *obj) |
| 869 | |
| 870 | Set the profiler function to *func*. The *obj* parameter is passed to the |
| 871 | function as its first parameter, and may be any Python object, or *NULL*. If |
| 872 | the profile function needs to maintain state, using a different value for *obj* |
| 873 | for each thread provides a convenient and thread-safe place to store it. The |
| 874 | profile function is called for all monitored events except the line-number |
| 875 | events. |
| 876 | |
| 877 | |
| 878 | .. cfunction:: void PyEval_SetTrace(Py_tracefunc func, PyObject *obj) |
| 879 | |
| 880 | Set the tracing function to *func*. This is similar to |
| 881 | :cfunc:`PyEval_SetProfile`, except the tracing function does receive line-number |
| 882 | events. |
| 883 | |
Christian Heimes | d8654cf | 2007-12-02 15:22:16 +0000 | [diff] [blame] | 884 | .. cfunction:: PyObject* PyEval_GetCallStats(PyObject *self) |
| 885 | |
| 886 | Return a tuple of function call counts. There are constants defined for the |
| 887 | positions within the tuple: |
| 888 | |
| 889 | +-------------------------------+-------+ |
| 890 | | Name | Value | |
| 891 | +===============================+=======+ |
| 892 | | :const:`PCALL_ALL` | 0 | |
| 893 | +-------------------------------+-------+ |
| 894 | | :const:`PCALL_FUNCTION` | 1 | |
| 895 | +-------------------------------+-------+ |
| 896 | | :const:`PCALL_FAST_FUNCTION` | 2 | |
| 897 | +-------------------------------+-------+ |
| 898 | | :const:`PCALL_FASTER_FUNCTION`| 3 | |
| 899 | +-------------------------------+-------+ |
| 900 | | :const:`PCALL_METHOD` | 4 | |
| 901 | +-------------------------------+-------+ |
| 902 | | :const:`PCALL_BOUND_METHOD` | 5 | |
| 903 | +-------------------------------+-------+ |
| 904 | | :const:`PCALL_CFUNCTION` | 6 | |
| 905 | +-------------------------------+-------+ |
| 906 | | :const:`PCALL_TYPE` | 7 | |
| 907 | +-------------------------------+-------+ |
| 908 | | :const:`PCALL_GENERATOR` | 8 | |
| 909 | +-------------------------------+-------+ |
| 910 | | :const:`PCALL_OTHER` | 9 | |
| 911 | +-------------------------------+-------+ |
| 912 | | :const:`PCALL_POP` | 10 | |
| 913 | +-------------------------------+-------+ |
| 914 | |
| 915 | :const:`PCALL_FAST_FUNCTION` means no argument tuple needs to be created. |
| 916 | :const:`PCALL_FASTER_FUNCTION` means that the fast-path frame setup code is used. |
| 917 | |
| 918 | If there is a method call where the call can be optimized by changing |
| 919 | the argument tuple and calling the function directly, it gets recorded |
| 920 | twice. |
| 921 | |
| 922 | This function is only present if Python is compiled with :const:`CALL_PROFILE` |
| 923 | defined. |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 924 | |
| 925 | .. _advanced-debugging: |
| 926 | |
| 927 | Advanced Debugger Support |
| 928 | ========================= |
| 929 | |
| 930 | .. sectionauthor:: Fred L. Drake, Jr. <fdrake@acm.org> |
| 931 | |
| 932 | |
| 933 | These functions are only intended to be used by advanced debugging tools. |
| 934 | |
| 935 | |
| 936 | .. cfunction:: PyInterpreterState* PyInterpreterState_Head() |
| 937 | |
| 938 | Return the interpreter state object at the head of the list of all such objects. |
| 939 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 940 | |
| 941 | .. cfunction:: PyInterpreterState* PyInterpreterState_Next(PyInterpreterState *interp) |
| 942 | |
| 943 | Return the next interpreter state object after *interp* from the list of all |
| 944 | such objects. |
| 945 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 946 | |
| 947 | .. cfunction:: PyThreadState * PyInterpreterState_ThreadHead(PyInterpreterState *interp) |
| 948 | |
| 949 | Return the a pointer to the first :ctype:`PyThreadState` object in the list of |
| 950 | threads associated with the interpreter *interp*. |
| 951 | |
Georg Brandl | 116aa62 | 2007-08-15 14:28:22 +0000 | [diff] [blame] | 952 | |
| 953 | .. cfunction:: PyThreadState* PyThreadState_Next(PyThreadState *tstate) |
| 954 | |
| 955 | Return the next thread state object after *tstate* from the list of all such |
| 956 | objects belonging to the same :ctype:`PyInterpreterState` object. |
| 957 | |