Lines Matching refs:Py_Initialize

15 In an application embedding  Python, the :c:func:`Py_Initialize` function must
62    :c:func:`Py_Initialize`: :c:func:`Py_EncodeLocale`, :c:func:`Py_GetPath`,
225 .. c:function:: void Py_Initialize()
259    This function works like :c:func:`Py_Initialize` if *initsigs* is ``1``. If
268    :c:func:`Py_Initialize` is called again.
273    Undo all initializations made by :c:func:`Py_Initialize` and subsequent use of
276    the last call to :c:func:`Py_Initialize`.  Ideally, this frees all memory
278    time (without calling :c:func:`Py_Initialize` again first).  Normally the
298    than once; this can happen if an application calls :c:func:`Py_Initialize` and
317       single: Py_Initialize()
321    This function should be called before :c:func:`Py_Initialize`, if it is
336    again in order to affect subsequent calls to :c:func:`Py_Initialize`.
347       single: Py_Initialize()
351    This function should be called before :c:func:`Py_Initialize` is called for
464    :c:func:`Py_Initialize`, then :c:func:`Py_GetPath` won't attempt to compute a
474    if required after calling :c:func:`Py_Initialize`.
759 interpreter (created automatically by :c:func:`Py_Initialize`).  Python
824       This function is now called by :c:func:`Py_Initialize()`, so you don't
828       This function cannot be called before :c:func:`Py_Initialize()` anymore.
840       The :term:`GIL` is now initialized by :c:func:`Py_Initialize()`.
975 All of the following functions must be called after :c:func:`Py_Initialize`.
978    :c:func:`Py_Initialize()` now initializes the :term:`GIL`.
1141       single: Py_Initialize()
1150    :c:func:`Py_FinalizeEx` and :c:func:`Py_Initialize`; in that case, the extension's