# German translations for Python package.

# Copyright (C) 2001 Python Software Foundation

# This file is distributed under the same license as the Python package.

# Automatically generated, 2026.

#

msgid ""

msgstr ""

"Project-Id-Version: Python 3.15\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2026-09-28 03:11+0000\n"

"PO-Revision-Date: 2026-09-23 06:17+0000\n"

"Last-Translator: Automatically generated\n"

"Language-Team: none\n"

"Language: de\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#: ../../c-api/interp-lifecycle.rst:6

msgid "Interpreter initialization and finalization"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:8

msgid ""

"See :ref:`Python Initialization Configuration <init-config>` for details on "

"how to configure the interpreter prior to initialization."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:14

msgid "Before Python initialization"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:16

msgid ""

"In an application embedding Python, the :c:func:`Py_Initialize` function "

"must be called before using any other Python/C API functions; with the "

"exception of a few functions and the :ref:`global configuration variables "

"<global-conf-vars>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:21

msgid ""

"The following functions can be safely called before Python is initialized:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:23

msgid "Functions that initialize the interpreter:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:25

msgid ":c:func:`Py_Initialize`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:26

msgid ":c:func:`Py_InitializeEx`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:27

msgid ":c:func:`Py_InitializeFromConfig`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:28

msgid ":c:func:`Py_BytesMain`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:29

msgid ":c:func:`Py_Main`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:30

msgid "the runtime pre-initialization functions covered in :ref:`init-config`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:32

msgid "Configuration functions:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:34

msgid ":c:func:`PyImport_AppendInittab`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:35

msgid ":c:func:`PyImport_ExtendInittab`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:36

msgid ":c:func:`!PyInitFrozenExtensions`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:37

msgid ":c:func:`PyMem_SetAllocator`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:38

msgid ":c:func:`PyMem_SetupDebugHooks`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:39

msgid ":c:func:`PyObject_SetArenaAllocator`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:40

msgid ":c:func:`Py_SetProgramName`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:41

msgid ":c:func:`Py_SetPythonHome`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:42

msgid "the configuration functions covered in :ref:`init-config`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:44

msgid "Informative functions:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:46 ../../c-api/interp-lifecycle.rst:54

msgid ":c:func:`Py_IsInitialized`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:47

msgid ":c:func:`PyMem_GetAllocator`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:48

msgid ":c:func:`PyObject_GetArenaAllocator`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:49

msgid ":c:func:`Py_GetBuildInfo`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:50

msgid ":c:func:`Py_GetCompiler`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:51

msgid ":c:func:`Py_GetCopyright`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:52

msgid ":c:func:`Py_GetPlatform`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:53

msgid ":c:func:`Py_GetVersion`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:56

msgid "Utilities:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:58

msgid ":c:func:`Py_DecodeLocale`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:59

msgid ""

"the status reporting and utility functions covered in :ref:`init-config`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:61

msgid "Memory allocators:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:63

msgid ":c:func:`PyMem_RawMalloc`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:64

msgid ":c:func:`PyMem_RawRealloc`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:65

msgid ":c:func:`PyMem_RawCalloc`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:66

msgid ":c:func:`PyMem_RawFree`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:68

msgid "Synchronization:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:70

msgid ":c:func:`PyMutex_Lock`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:71

msgid ":c:func:`PyMutex_Unlock`"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:75

msgid ""

"Despite their apparent similarity to some of the functions listed above, the "

"following functions **should not be called** before the interpreter has been "

"initialized: :c:func:`Py_EncodeLocale`, :c:func:`PyEval_InitThreads`, and :c:"

"func:`Py_RunMain`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:84

msgid "Global configuration variables"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:86

msgid ""

"Python has variables for the global configuration to control different "

"features and options. By default, these flags are controlled by :ref:"

"`command line options <using-on-interface-options>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:90

msgid ""

"When a flag is set by an option, the value of the flag is the number of "

"times that the option was set. For example, ``-b`` sets :c:data:"

"`Py_BytesWarningFlag` to 1 and ``-bb`` sets :c:data:`Py_BytesWarningFlag` to "

"2."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:97

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"bytes_warning` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:101

msgid ""

"Issue a warning when comparing :class:`bytes` or :class:`bytearray` with :"

"class:`str` or :class:`bytes` with :class:`int`. Issue an error if greater "

"or equal to ``2``."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:105

msgid "Set by the :option:`-b` option."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:112

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"parser_debug` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:116

msgid ""

"Turn on parser debugging output (for expert only, depending on compilation "

"options)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:119

msgid ""

"Set by the :option:`-d` option and the :envvar:`PYTHONDEBUG` environment "

"variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:127

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"write_bytecode` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:131

msgid ""

"If set to non-zero, Python won't try to write ``.pyc`` files on the import "

"of source modules."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:134

msgid ""

"Set by the :option:`-B` option and the :envvar:`PYTHONDONTWRITEBYTECODE` "

"environment variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:142

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"pathconfig_warnings` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:146

msgid "Private flag used by ``_freeze_module`` and ``frozenmain`` programs."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:153

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"hash_seed` and :c:member:`PyConfig.use_hash_seed` should be used instead, "

"see :ref:`Python Initialization Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:158

msgid ""

"Set to ``1`` if the :envvar:`PYTHONHASHSEED` environment variable is set to "

"a non-empty string."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:161

msgid ""

"If the flag is non-zero, read the :envvar:`PYTHONHASHSEED` environment "

"variable to initialize the secret hash seed."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:169

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"use_environment` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:173

msgid ""

"Ignore all :envvar:`!PYTHON*` environment variables, e.g. :envvar:"

"`PYTHONPATH` and :envvar:`PYTHONHOME`, that might be set."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:176

msgid "Set by the :option:`-E` and :option:`-I` options."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:183

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"inspect` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:187

msgid ""

"When a script is passed as first argument or the :option:`-c` option is "

"used, enter interactive mode after executing the script or the command, even "

"when :data:`sys.stdin` does not appear to be a terminal."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:191

msgid ""

"Set by the :option:`-i` option and the :envvar:`PYTHONINSPECT` environment "

"variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:199

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"interactive` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:203

msgid "Set by the :option:`-i` option."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:210

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"isolated` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:214

msgid ""

"Run Python in isolated mode. In isolated mode :data:`sys.path` contains "

"neither the script's directory nor the user's site-packages directory."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:217

msgid "Set by the :option:`-I` option."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:226

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyPreConfig."

"legacy_windows_fs_encoding` should be used instead, see :ref:`Python "

"Initialization Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:230

msgid ""

"If the flag is non-zero, use the ``mbcs`` encoding with ``replace`` error "

"handler, instead of the UTF-8 encoding with ``surrogatepass`` error handler, "

"for the :term:`filesystem encoding and error handler`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:234

msgid ""

"Set to ``1`` if the :envvar:`PYTHONLEGACYWINDOWSFSENCODING` environment "

"variable is set to a non-empty string."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:237

msgid "See :pep:`529` for more details."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:239 ../../c-api/interp-lifecycle.rst:258

msgid "Availability"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:246

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"legacy_windows_stdio` should be used instead, see :ref:`Python "

"Initialization Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:250

msgid ""

"If the flag is non-zero, use :class:`io.FileIO` instead of :class:`!io."

"_WindowsConsoleIO` for :mod:`sys` standard streams."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:253

msgid ""

"Set to ``1`` if the :envvar:`PYTHONLEGACYWINDOWSSTDIO` environment variable "

"is set to a non-empty string."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:256

msgid "See :pep:`528` for more details."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:265

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"site_import` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:269

msgid ""

"Disable the import of the module :mod:`site` and the site-dependent "

"manipulations of :data:`sys.path` that it entails. Also disable these "

"manipulations if :mod:`site` is explicitly imported later (call :func:`site."

"main` if you want them to be triggered)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:274

msgid "Set by the :option:`-S` option."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:281

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"user_site_directory` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:285

msgid ""

"Don't add the :data:`user site-packages directory <site.USER_SITE>` to :data:"

"`sys.path`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:288

msgid ""

"Set by the :option:`-s` and :option:`-I` options, and the :envvar:"

"`PYTHONNOUSERSITE` environment variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:296

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"optimization_level` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:300

msgid ""

"Set by the :option:`-O` option and the :envvar:`PYTHONOPTIMIZE` environment "

"variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:308

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"quiet` should be used instead, see :ref:`Python Initialization Configuration "

"<init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:312

msgid ""

"Don't display the copyright and version messages even in interactive mode."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:314

msgid "Set by the :option:`-q` option."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:323

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"buffered_stdio` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:327

msgid "Force the stdout and stderr streams to be unbuffered."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:329

msgid ""

"Set by the :option:`-u` option and the :envvar:`PYTHONUNBUFFERED` "

"environment variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:337

msgid ""

"This API is kept for backward compatibility: setting :c:member:`PyConfig."

"verbose` should be used instead, see :ref:`Python Initialization "

"Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:341

msgid ""

"Print a message each time a module is initialized, showing the place "

"(filename or built-in module) from which it is loaded. If greater or equal "

"to ``2``, print a message for each file that is checked for when searching "

"for a module. Also provides information on module cleanup at exit."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:346

msgid ""

"Set by the :option:`-v` option and the :envvar:`PYTHONVERBOSE` environment "

"variable."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:353

msgid "Initializing and finalizing the interpreter"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:367

msgid ""

"Initialize the Python interpreter. In an application embedding Python, this "

"should be called before using any other Python/C API functions; see :ref:"

"`Before Python Initialization <pre-init-safe>` for the few exceptions."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:371

msgid ""

"This initializes the table of loaded modules (``sys.modules``), and creates "

"the fundamental modules :mod:`builtins`, :mod:`__main__` and :mod:`sys`. It "

"also initializes the module search path (``sys.path``). It does not set "

"``sys.argv``; use the :ref:`Python Initialization Configuration <init-"

"config>` API for that. This is a no-op when called for a second time "

"(without calling :c:func:`Py_FinalizeEx` first). There is no return value; "

"it is a fatal error if the initialization fails."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:379 ../../c-api/interp-lifecycle.rst:393

msgid ""

"Use :c:func:`Py_InitializeFromConfig` to customize the :ref:`Python "

"Initialization Configuration <init-config>`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:383

msgid ""

"On Windows, changes the console mode from ``O_TEXT`` to ``O_BINARY``, which "

"will also affect non-Python uses of the console using the C Runtime."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:389

msgid ""

"This function works like :c:func:`Py_Initialize` if *initsigs* is ``1``. If "

"*initsigs* is ``0``, it skips initialization registration of signal "

"handlers, which may be useful when CPython is embedded as part of a larger "

"application."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:399

msgid ""

"Initialize Python from *config* configuration, as described in :ref:`init-"

"from-config`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:402

msgid ""

"See the :ref:`init-config` section for details on pre-initializing the "

"interpreter, populating the runtime configuration structure, and querying "

"the returned status structure."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:409

msgid ""

"Return true (nonzero) when the Python interpreter has been initialized, "

"false (zero) if not. After :c:func:`Py_FinalizeEx` is called, this returns "

"false until :c:func:`Py_Initialize` is called again."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:413

msgid ""

"This function no longer returns true until initialization has fully "

"completed, including import of the :mod:`site` module. Previously it could "

"return true while :c:func:`Py_Initialize` was still running."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:421

msgid ""

"Return true (non-zero) if the main Python interpreter is :term:`shutting "

"down <interpreter shutdown>`. Return false (zero) otherwise."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:429

msgid ""

"Undo all initializations made by :c:func:`Py_Initialize` and subsequent use "

"of Python/C API functions, and destroy all sub-interpreters (see :c:func:"

"`Py_NewInterpreter` below) that were created and not yet destroyed since the "

"last call to :c:func:`Py_Initialize`. This is a no-op when called for a "

"second time (without calling :c:func:`Py_Initialize` again first)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:435

msgid ""

"Since this is the reverse of :c:func:`Py_Initialize`, it should be called in "

"the same thread with the same interpreter active. That means the main "

"thread and the main interpreter. This should never be called while :c:func:"

"`Py_RunMain` is running."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:440

msgid ""

"Normally the return value is ``0``. If there were errors during finalization "

"(flushing buffered data), ``-1`` is returned."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:444

msgid ""

"Note that Python will do a best effort at freeing all memory allocated by "

"the Python interpreter. Therefore, any C-Extension should make sure to "

"correctly clean up all of the previously allocated PyObjects before using "

"them in subsequent calls to :c:func:`Py_Initialize`. Otherwise it could "

"introduce vulnerabilities and incorrect behavior."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:450

msgid ""

"This function is provided for a number of reasons. An embedding application "

"might want to restart Python without having to restart the application "

"itself. An application that has loaded the Python interpreter from a "

"dynamically loadable library (or DLL) might want to free all memory "

"allocated by Python before unloading the DLL. During a hunt for memory leaks "

"in an application a developer might want to free all memory allocated by "

"Python before exiting from the application."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:458

msgid ""

"**Bugs and caveats:** The destruction of modules and objects in modules is "

"done in random order; this may cause destructors (:meth:`~object.__del__` "

"methods) to fail when they depend on other objects (even functions) or "

"modules. Dynamically loaded extension modules loaded by Python are not "

"unloaded. Small amounts of memory allocated by the Python interpreter may "

"not be freed (if you find a leak, please report it). Memory tied up in "

"circular references between objects is not freed. Interned strings will all "

"be deallocated regardless of their reference count. Some memory allocated by "

"extension modules may not be freed. Some extensions may not work properly "

"if their initialization routine is called more than once; this can happen if "

"an application calls :c:func:`Py_Initialize` and :c:func:`Py_FinalizeEx` "

"more than once. :c:func:`Py_FinalizeEx` must not be called recursively from "

"within itself. Therefore, it must not be called by any code that may be run "

"as part of the interpreter shutdown process, such as :py:mod:`atexit` "

"handlers, object finalizers, or any code that may be run while flushing the "

"stdout and stderr files."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:474

msgid ""

"Raises an :ref:`auditing event <auditing>` ``cpython."

"_PySys_ClearAuditHooks`` with no arguments."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:481

msgid ""

"This is a backwards-compatible version of :c:func:`Py_FinalizeEx` that "

"disregards the return value."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:487

msgid ""

"Similar to :c:func:`Py_Main` but *argv* is an array of bytes strings, "

"allowing the calling application to delegate the text decoding step to the "

"CPython runtime."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:496

msgid ""

"The main program for the standard interpreter, encapsulating a full "

"initialization/finalization cycle, as well as additional behaviour to "

"implement reading configurations settings from the environment and command "

"line, and then executing ``__main__`` in accordance with :ref:`using-on-"

"cmdline`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:502

msgid ""

"This is made available for programs which wish to support the full CPython "

"command line interface, rather than just embedding a Python runtime in a "

"larger application."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:506

msgid ""

"The *argc* and *argv* parameters are similar to those which are passed to a "

"C program's :c:func:`main` function, except that the *argv* entries are "

"first converted to ``wchar_t`` using :c:func:`Py_DecodeLocale`. It is also "

"important to note that the argument list entries may be modified to point to "

"strings other than those passed in (however, the contents of the strings "

"pointed to by the argument list are not modified)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:513

msgid ""

"The return value is ``2`` if the argument list does not represent a valid "

"Python command line, and otherwise the same as :c:func:`Py_RunMain`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:516

msgid ""

"In terms of the CPython runtime configuration APIs documented in the :ref:"

"`runtime configuration <init-config>` section (and without accounting for "

"error handling), ``Py_Main`` is approximately equivalent to::"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:520

msgid ""

"PyConfig config;\n"

"PyConfig_InitPythonConfig(&config);\n"

"PyConfig_SetArgv(&config, argc, argv);\n"

"Py_InitializeFromConfig(&config);\n"

"PyConfig_Clear(&config);\n"

"\n"

"Py_RunMain();"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:528

msgid ""

"In normal usage, an embedding application will call this function *instead* "

"of calling :c:func:`Py_Initialize`, :c:func:`Py_InitializeEx` or :c:func:"

"`Py_InitializeFromConfig` directly, and all settings will be applied as "

"described elsewhere in this documentation. If this function is instead "

"called *after* a preceding runtime initialization API call, then exactly "

"which environmental and command line configuration settings will be updated "

"is version dependent (as it depends on which settings correctly support "

"being modified after they have already been set once when the runtime was "

"first initialized)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:541

msgid "Executes the main module in a fully configured CPython runtime."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:543

msgid ""

"Executes the command (:c:member:`PyConfig.run_command`), the script (:c:"

"member:`PyConfig.run_filename`) or the module (:c:member:`PyConfig."

"run_module`) specified on the command line or in the configuration. If none "

"of these values are set, runs the interactive Python prompt (REPL) using the "

"``__main__`` module's global namespace."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:549

msgid ""

"If :c:member:`PyConfig.inspect` is not set (the default), the return value "

"will be ``0`` if the interpreter exits normally (that is, without raising an "

"exception), the exit status of an unhandled :exc:`SystemExit`, or ``1`` for "

"any other unhandled exception."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:554

msgid ""

"If :c:member:`PyConfig.inspect` is set (such as when the :option:`-i` option "

"is used), rather than returning when the interpreter exits, execution will "

"instead resume in an interactive Python prompt (REPL) using the ``__main__`` "

"module's global namespace. If the interpreter exited with an exception, it "

"is immediately raised in the REPL session. The function return value is then "

"determined by the way the *REPL session* terminates: ``0``, ``1``, or the "

"status of a :exc:`SystemExit`, as specified above."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:562

msgid ""

"This function always finalizes the Python interpreter before it returns."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:564

msgid ""

"See :ref:`Python Configuration <init-python-config>` for an example of a "

"customized Python that always runs in isolated mode using :c:func:"

"`Py_RunMain`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:570

msgid ""

"Register an :mod:`atexit` callback for the target interpreter *interp*. This "

"is similar to :c:func:`Py_AtExit`, but takes an explicit interpreter and "

"data pointer for the callback."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:574

msgid "There must be an :term:`attached thread state` for *interp*."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:582

msgid "Cautions regarding interpreter finalization"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:584

msgid ""

"In the late stage of :term:`interpreter shutdown`, after attempting to wait "

"for non-daemon threads to exit (though this can be interrupted by :class:"

"`KeyboardInterrupt`) and running the :mod:`atexit` functions, the runtime is "

"marked as finalizing, meaning that :c:func:`Py_IsFinalizing` and :func:`sys."

"is_finalizing` return true. At this point, only the finalization thread "

"(the thread that initiated finalization; this is typically the main thread) "

"is allowed to :term:`attach <attached thread state>` a thread state."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:592

msgid ""

"Other threads that attempt to attach during finalization, either explicitly "

"(such as via :c:func:`PyThreadState_Ensure` or :c:macro:"

"`Py_END_ALLOW_THREADS`) or implicitly (such as in-between bytecode "

"instructions), will enter a **permanently blocked state**. Generally, this "

"is harmless, but this can result in deadlocks. For example, a thread may be "

"permanently blocked while holding a lock, meaning that the finalization "

"thread can never acquire that lock."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:600

msgid ""

"Prior to CPython 3.13, the thread would exit instead of hanging, which led "

"to other issues (see the warning note at :c:func:`PyThread_exit_thread`)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:604

msgid ""

"Gross? Yes. Starting in Python 3.15, there are a number of C APIs that make "

"it possible to avoid these issues by temporarily preventing finalization:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:611

msgid ""

":pep:`788` explains the design, motivation and rationale for these APIs."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:616

msgid "An opaque interpreter guard structure."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:618

msgid ""

"By holding an interpreter guard, the caller can ensure that the interpreter "

"will not finalize until the guard is closed (through :c:func:"

"`PyInterpreterGuard_Close`)."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:622

msgid ""

"When a guard is held, a thread attempting to finalize the interpreter will "

"block until the guard is closed before starting finalization. After "

"finalization has started, threads are forever unable to acquire guards for "

"that interpreter. This means that if you forget to close an interpreter "

"guard, the process will **permanently hang** during finalization!"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:629

msgid ""

"Holding a guard for an interpreter is similar to holding a :term:`strong "

"reference` to a Python object, except finalization does not happen "

"automatically after all guards are released: it requires an explicit :c:func:"

"`Py_EndInterpreter` call."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:639

msgid ""

"Create a finalization guard for the current interpreter. This will prevent "

"finalization until the guard is closed."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:642

msgid "For example:"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:644

msgid ""

"// Temporarily prevent finalization.\n"

"PyInterpreterGuard *guard = PyInterpreterGuard_FromCurrent();\n"

"if (guard == NULL) {\n"

" // Finalization has already started or we're out of memory.\n"

" return NULL;\n"

"}\n"

"\n"

"Py_BEGIN_ALLOW_THREADS;\n"

"// Do some critical processing here. For example, we can safely acquire\n"

"// locks that might be acquired by the finalization thread.\n"

"Py_END_ALLOW_THREADS;\n"

"\n"

"// Now that we're done with our critical processing, the interpreter is\n"

"// allowed to finalize again.\n"

"PyInterpreterGuard_Close(guard);"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:662

msgid ""

"On success, this function returns a guard for the current interpreter; on "

"failure, it returns ``NULL`` with an exception set."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:665

msgid ""

"This function will fail only if the current interpreter has already started "

"finalizing, or if the process is out of memory."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:668

msgid ""

"The guard pointer returned by this function must be eventually closed with :"

"c:func:`PyInterpreterGuard_Close`; failing to do so will result in the "

"Python process infinitely hanging."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:672 ../../c-api/interp-lifecycle.rst:739

msgid "The caller must hold an :term:`attached thread state`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:679

msgid "Create a finalization guard for an interpreter through a view."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:681

msgid ""

"On success, this function returns a guard to the interpreter represented by "

"*view*. The view is still valid after calling this function. The guard must "

"eventually be closed with :c:func:`PyInterpreterGuard_Close`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:686

msgid ""

"If the interpreter no longer exists, is already finalizing, or out of "

"memory, then this function returns ``NULL`` without setting an exception."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:689 ../../c-api/interp-lifecycle.rst:775

msgid "The caller does not need to hold an :term:`attached thread state`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:696

msgid ""

"Close an interpreter guard, allowing the interpreter to start finalization "

"if no other guards remain. If an interpreter guard is never closed, the "

"interpreter will infinitely wait when trying to enter finalization!"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:701

msgid ""

"After an interpreter guard is closed, it may not be used in :c:func:"

"`PyThreadState_Ensure`. Doing so will result in undefined behavior."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:705 ../../c-api/interp-lifecycle.rst:752

msgid ""

"This function cannot fail, and the caller doesn't need to hold an :term:"

"`attached thread state`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:714

msgid "Interpreter views"

msgstr ""

#: ../../c-api/interp-lifecycle.rst:716

msgid ""

"In some cases, it may be necessary to access an interpreter that may have "

"been deleted. This can be done using interpreter views."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:721

msgid "An opaque view of an interpreter."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:723

msgid ""

"This is a thread-safe way to access an interpreter that may have be "

"finalizing or already destroyed."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:731

msgid "Create a view to the current interpreter."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:733

msgid ""

"This function is generally meant to be used alongside :c:func:"

"`PyInterpreterGuard_FromView` or :c:func:`PyThreadState_EnsureFromView`."

msgstr ""

#: ../../c-api/interp-lifecycle.rst:736

msgid ""

"On success, this function returns a view to the current interpreter; on "