Searched refs:Py_Initialize (Results 1 – 25 of 35) sorted by relevance
12
/third_party/python/Doc/c-api/ |
D | init.rst | 17 In an application embedding Python, the :c:func:`Py_Initialize` function must 65 :c:func:`Py_Initialize`: :c:func:`Py_EncodeLocale`, :c:func:`Py_GetPath`, 229 .. c:function:: void Py_Initialize() 263 This function works like :c:func:`Py_Initialize` if *initsigs* is ``1``. If 272 :c:func:`Py_Initialize` is called again. 277 Undo all initializations made by :c:func:`Py_Initialize` and subsequent use of 280 the last call to :c:func:`Py_Initialize`. Ideally, this frees all memory 282 time (without calling :c:func:`Py_Initialize` again first). Normally the 302 than once; this can happen if an application calls :c:func:`Py_Initialize` and 322 single: Py_Initialize() [all …]
|
D | sys.rst | 236 called prior to :c:func:`Py_Initialize`. 241 to :c:func:`Py_Initialize` in order to affect the warnings filter list. 249 :mod:`warnings` in :c:func:`Py_Initialize` to be effective, but can't be 299 may be called prior to :c:func:`Py_Initialize`. 350 This function is safe to call before :c:func:`Py_Initialize`. When called
|
D | intro.rst | 665 single: Py_Initialize() 672 The basic initialization function is :c:func:`Py_Initialize`. This initializes 679 :c:func:`Py_Initialize` does not set the "script argument list" (``sys.argv``). 682 after the call to :c:func:`Py_Initialize`. 685 slightly different), :c:func:`Py_Initialize` calculates the module search path 709 ``Py_SetProgramName(file)`` *before* calling :c:func:`Py_Initialize`. Note that 720 :c:func:`Py_Initialize`) or the application is simply done with its use of
|
D | file.rst | 83 This function is safe to call before :c:func:`Py_Initialize`.
|
D | import.rst | 277 :c:func:`Py_Initialize`. 302 internal table. This must be called before :c:func:`Py_Initialize`.
|
/third_party/python/Programs/ |
D | _testembed.c | 31 Py_Initialize(); in _testembed_Py_Initialize() 146 Py_Initialize(); in test_forced_io_encoding() 181 Py_Initialize(); in test_pre_initialization_api() 302 Py_Initialize(); in test_initialize_twice() 475 Py_Initialize(); in test_init_global_config() 1423 Py_Initialize(); in test_init_setpath() 1485 Py_Initialize(); in test_init_setpythonhome()
|
/third_party/python/Misc/NEWS.d/ |
D | 3.7.0.rst | 16 Calling Py_Initialize() twice does nothing, instead of failing with a fatal
|
D | 3.7.0b3.rst | 531 PySys_AddWarnOption, and PySys_AddXOption prior to calling Py_Initialize.
|
D | 3.10.0a5.rst | 112 :c:func:`Py_Initialize` / :c:func:`Py_Finalize` is called multiple times:
|
D | 3.10.0a3.rst | 1401 :c:func:`Py_Initialize` (before Python is initialized). Use the new 1437 When :c:func:`Py_Initialize` is called twice, the second call now updates
|
D | 3.7.0a4.rst | 816 Py_Initialize() doesn't reset the memory allocators to default if the
|
D | 3.7.0b1.rst | 182 Py_Initialize() now creates the GIL. The GIL is no longer created "on
|
/third_party/python/Doc/extending/ |
D | embedding.rst | 28 the very least, you have to call the function :c:func:`Py_Initialize`. There are 68 Py_Initialize(); 79 :c:func:`Py_Initialize` to inform the interpreter about paths to Python run-time 81 :c:func:`Py_Initialize`, followed by the execution of a hard-coded Python script 173 Py_Initialize(); 247 following two statements before the call to :c:func:`Py_Initialize`::
|
/third_party/python/Include/ |
D | pylifecycle.h | 12 PyAPI_FUNC(void) Py_Initialize(void);
|
/third_party/python/Doc/includes/ |
D | run-func.c | 16 Py_Initialize(); in main()
|
/third_party/python/Mac/Tools/ |
D | pythonw.c | 65 if (dladdr(Py_Initialize, &info) == 0) { in get_python_path()
|
/third_party/python/Modules/_ctypes/ |
D | callbacks.c | 471 Py_Initialize(); in LoadPython()
|
/third_party/python/PC/ |
D | python3dll.c | 73 EXPORT_FUNC(Py_Initialize)
|
/third_party/python/Doc/data/ |
D | stable_abi.dat | 807 function,Py_Initialize,3.2,
|
/third_party/python/Doc/faq/ |
D | extending.rst | 307 Py_Initialize ();
|
D | windows.rst | 217 Py_Initialize(); // Initialize Python.
|
/third_party/alsa-lib/modules/mixer/simple/ |
D | python.c | 1135 Py_Initialize(); in alsa_mixer_simple_finit()
|
/third_party/python/Python/ |
D | pylifecycle.c | 1264 Py_Initialize(void) in Py_Initialize() function
|
/third_party/python/Doc/whatsnew/ |
D | 3.7.rst | 1721 :c:func:`Py_Initialize` before calling most C API functions is now 2499 calling `Py_Initialize`. Use :c:func:`PySys_AddWarnOption` instead. 2525 Starting in 3.7.1, :c:func:`Py_Initialize` now consistently reads and respects 2530 calling :c:func:`Py_Initialize`.
|
/third_party/python/Misc/ |
D | stable_abi.txt | 1544 function Py_Initialize
|
12