Melcore/python-docs-fr
1
0
Fork 0
forked from AFPy/python-docs-fr
Code Pull Requests Activity
294e8b93c0
python-docs-fr/c-api/init.po
Jules Lasne (jlasne) 294e8b93c0
Make Merge a3488e5902f5c26e5cc289aec2518e7b5058e5d1 (#729) 
* make merge

* Update distributing/index.po

* Update extending/extending.po

* Apply suggestions from code review

* powrap
2019-05-23 18:59:19 +02:00

1861 lines
64 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Copyright (C) 2001-2018, Python Software Foundation
# For licence information, see README file.
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-05-23 16:48+0200\n"
"PO-Revision-Date: 2018-11-29 18:22+0100\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/c-api/init.rst:8
msgid "Initialization, Finalization, and Threads"
msgstr ""
#: ../Doc/c-api/init.rst:13
msgid "Before Python Initialization"
msgstr ""
#: ../Doc/c-api/init.rst:15
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 ""
#: ../Doc/c-api/init.rst:20
msgid ""
"The following functions can be safely called before Python is initialized:"
msgstr ""
#: ../Doc/c-api/init.rst:22
msgid "Configuration functions:"
msgstr ""
#: ../Doc/c-api/init.rst:24
msgid ":c:func:`PyImport_AppendInittab`"
msgstr ""
#: ../Doc/c-api/init.rst:25
msgid ":c:func:`PyImport_ExtendInittab`"
msgstr ""
#: ../Doc/c-api/init.rst:26
msgid ":c:func:`PyInitFrozenExtensions`"
msgstr ""
#: ../Doc/c-api/init.rst:27
msgid ":c:func:`PyMem_SetAllocator`"
msgstr ""
#: ../Doc/c-api/init.rst:28
msgid ":c:func:`PyMem_SetupDebugHooks`"
msgstr ""
#: ../Doc/c-api/init.rst:29
msgid ":c:func:`PyObject_SetArenaAllocator`"
msgstr ""
#: ../Doc/c-api/init.rst:30
msgid ":c:func:`Py_SetPath`"
msgstr ""
#: ../Doc/c-api/init.rst:31
msgid ":c:func:`Py_SetProgramName`"
msgstr ""
#: ../Doc/c-api/init.rst:32
msgid ":c:func:`Py_SetPythonHome`"
msgstr ""
#: ../Doc/c-api/init.rst:33
msgid ":c:func:`Py_SetStandardStreamEncoding`"
msgstr ""
#: ../Doc/c-api/init.rst:34
msgid ":c:func:`PySys_AddWarnOption`"
msgstr ""
#: ../Doc/c-api/init.rst:35
msgid ":c:func:`PySys_AddXOption`"
msgstr ""
#: ../Doc/c-api/init.rst:36
msgid ":c:func:`PySys_ResetWarnOptions`"
msgstr ""
#: ../Doc/c-api/init.rst:38
msgid "Informative functions:"
msgstr ""
#: ../Doc/c-api/init.rst:40
msgid ":c:func:`Py_IsInitialized`"
msgstr ""
#: ../Doc/c-api/init.rst:41
msgid ":c:func:`PyMem_GetAllocator`"
msgstr ""
#: ../Doc/c-api/init.rst:42
msgid ":c:func:`PyObject_GetArenaAllocator`"
msgstr ""
#: ../Doc/c-api/init.rst:43
msgid ":c:func:`Py_GetBuildInfo`"
msgstr ""
#: ../Doc/c-api/init.rst:44
msgid ":c:func:`Py_GetCompiler`"
msgstr ""
#: ../Doc/c-api/init.rst:45
msgid ":c:func:`Py_GetCopyright`"
msgstr ""
#: ../Doc/c-api/init.rst:46
msgid ":c:func:`Py_GetPlatform`"
msgstr ""
#: ../Doc/c-api/init.rst:47
msgid ":c:func:`Py_GetVersion`"
msgstr ""
#: ../Doc/c-api/init.rst:49
msgid "Utilities:"
msgstr ""
#: ../Doc/c-api/init.rst:51
msgid ":c:func:`Py_DecodeLocale`"
msgstr ""
#: ../Doc/c-api/init.rst:53
msgid "Memory allocators:"
msgstr ""
#: ../Doc/c-api/init.rst:55
msgid ":c:func:`PyMem_RawMalloc`"
msgstr ""
#: ../Doc/c-api/init.rst:56
msgid ":c:func:`PyMem_RawRealloc`"
msgstr ""
#: ../Doc/c-api/init.rst:57
msgid ":c:func:`PyMem_RawCalloc`"
msgstr ""
#: ../Doc/c-api/init.rst:58
msgid ":c:func:`PyMem_RawFree`"
msgstr ""
#: ../Doc/c-api/init.rst:62
msgid ""
"The following functions **should not be called** before :c:func:"
"`Py_Initialize`: :c:func:`Py_EncodeLocale`, :c:func:`Py_GetPath`, :c:func:"
"`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, :c:func:"
"`Py_GetProgramFullPath`, :c:func:`Py_GetPythonHome`, :c:func:"
"`Py_GetProgramName` and :c:func:`PyEval_InitThreads`."
msgstr ""
#: ../Doc/c-api/init.rst:72
msgid "Global configuration variables"
msgstr ""
#: ../Doc/c-api/init.rst:74
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 ""
#: ../Doc/c-api/init.rst:78
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 ""
#: ../Doc/c-api/init.rst:84
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 ""
#: ../Doc/c-api/init.rst:88
msgid "Set by the :option:`-b` option."
msgstr ""
#: ../Doc/c-api/init.rst:92
msgid ""
"Turn on parser debugging output (for expert only, depending on compilation "
"options)."
msgstr ""
#: ../Doc/c-api/init.rst:95
msgid ""
"Set by the :option:`-d` option and the :envvar:`PYTHONDEBUG` environment "
"variable."
msgstr ""
#: ../Doc/c-api/init.rst:100
msgid ""
"If set to non-zero, Python won't try to write ``.pyc`` files on the import "
"of source modules."
msgstr ""
#: ../Doc/c-api/init.rst:103
msgid ""
"Set by the :option:`-B` option and the :envvar:`PYTHONDONTWRITEBYTECODE` "
"environment variable."
msgstr ""
#: ../Doc/c-api/init.rst:108
msgid ""
"Suppress error messages when calculating the module search path in :c:func:"
"`Py_GetPath`."
msgstr ""
#: ../Doc/c-api/init.rst:111
msgid "Private flag used by ``_freeze_importlib`` and ``frozenmain`` programs."
msgstr ""
#: ../Doc/c-api/init.rst:115
msgid ""
"Set to ``1`` if the :envvar:`PYTHONHASHSEED` environment variable is set to "
"a non-empty string."
msgstr ""
#: ../Doc/c-api/init.rst:118
msgid ""
"If the flag is non-zero, read the :envvar:`PYTHONHASHSEED` environment "
"variable to initialize the secret hash seed."
msgstr ""
#: ../Doc/c-api/init.rst:123
msgid ""
"Ignore all :envvar:`PYTHON*` environment variables, e.g. :envvar:"
"`PYTHONPATH` and :envvar:`PYTHONHOME`, that might be set."
msgstr ""
"Ignore toutes les variables d'environnement :envvar:`PYTHON*` qui pourraient "
"être définies. Par exemple, :envvar:`PYTHONPATH` et :envvar:`PYTHONHOME`."
#: ../Doc/c-api/init.rst:126
msgid "Set by the :option:`-E` and :option:`-I` options."
msgstr ""
#: ../Doc/c-api/init.rst:130
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 ""
#: ../Doc/c-api/init.rst:134
msgid ""
"Set by the :option:`-i` option and the :envvar:`PYTHONINSPECT` environment "
"variable."
msgstr ""
#: ../Doc/c-api/init.rst:139
msgid "Set by the :option:`-i` option."
msgstr ""
#: ../Doc/c-api/init.rst:143
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 ""
#: ../Doc/c-api/init.rst:146
msgid "Set by the :option:`-I` option."
msgstr ""
#: ../Doc/c-api/init.rst:152
msgid ""
"If the flag is non-zero, use the ``mbcs`` encoding instead of the UTF-8 "
"encoding for the filesystem encoding."
msgstr ""
#: ../Doc/c-api/init.rst:155
msgid ""
"Set to ``1`` if the :envvar:`PYTHONLEGACYWINDOWSFSENCODING` environment "
"variable is set to a non-empty string."
msgstr ""
#: ../Doc/c-api/init.rst:158
msgid "See :pep:`529` for more details."
msgstr "Voir la :pep:`529` pour plus d'informations."
#: ../Doc/c-api/init.rst:160 ../Doc/c-api/init.rst:172
msgid ":ref:`Availability <availability>`: Windows."
msgstr ":ref:`Disponibilité <availability>` : Windows."
#: ../Doc/c-api/init.rst:164
msgid ""
"If the flag is non-zero, use :class:`io.FileIO` instead of :class:"
"`WindowsConsoleIO` for :mod:`sys` standard streams."
msgstr ""
#: ../Doc/c-api/init.rst:167
msgid ""
"Set to ``1`` if the :envvar:`PYTHONLEGACYWINDOWSSTDIO` environment variable "
"is set to a non-empty string."
msgstr ""
#: ../Doc/c-api/init.rst:170
msgid "See :pep:`528` for more details."
msgstr ""
#: ../Doc/c-api/init.rst:176
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 ""
"Désactive l’importation du module :mod:`site` et les modifications locales "
"de :data:`sys.path` qu’il implique. Désactive aussi ces manipulations si :"
"mod:`site` est importé explicitement plus tard (appelez :func:`site.main` si "
"vous voulez les déclencher)."
#: ../Doc/c-api/init.rst:181
msgid "Set by the :option:`-S` option."
msgstr ""
#: ../Doc/c-api/init.rst:185
msgid ""
"Don't add the :data:`user site-packages directory <site.USER_SITE>` to :data:"
"`sys.path`."
msgstr ""
"N'ajoute pas le répertoire utilisateur :data:`site-packages <site."
"USER_SITE>` à :data:`sys.path`."
#: ../Doc/c-api/init.rst:188
msgid ""
"Set by the :option:`-s` and :option:`-I` options, and the :envvar:"
"`PYTHONNOUSERSITE` environment variable."
msgstr ""
#: ../Doc/c-api/init.rst:193
msgid ""
"Set by the :option:`-O` option and the :envvar:`PYTHONOPTIMIZE` environment "
"variable."
msgstr ""
#: ../Doc/c-api/init.rst:198
msgid ""
"Don't display the copyright and version messages even in interactive mode."
msgstr "N'affiche pas le copyright et la version, même en mode interactif."
#: ../Doc/c-api/init.rst:200
msgid "Set by the :option:`-q` option."
msgstr ""
#: ../Doc/c-api/init.rst:206
msgid "Force the stdout and stderr streams to be unbuffered."
msgstr ""
#: ../Doc/c-api/init.rst:208
msgid ""
"Set by the :option:`-u` option and the :envvar:`PYTHONUNBUFFERED` "
"environment variable."
msgstr ""
#: ../Doc/c-api/init.rst:213
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 ""
#: ../Doc/c-api/init.rst:218
msgid ""
"Set by the :option:`-v` option and the :envvar:`PYTHONVERBOSE` environment "
"variable."
msgstr ""
#: ../Doc/c-api/init.rst:223
msgid "Initializing and finalizing the interpreter"
msgstr ""
#: ../Doc/c-api/init.rst:241
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 ""
#: ../Doc/c-api/init.rst:245
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 :c:func:`PySys_SetArgvEx` 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 ""
#: ../Doc/c-api/init.rst:254
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 ""
#: ../Doc/c-api/init.rst:260
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 might be useful when Python is embedded."
msgstr ""
#: ../Doc/c-api/init.rst:267
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 ""
#: ../Doc/c-api/init.rst:274
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`. Ideally, this frees all memory "
"allocated by the Python interpreter. This is a no-op when called for a "
"second time (without calling :c:func:`Py_Initialize` again first). Normally "
"the return value is ``0``. If there were errors during finalization "
"(flushing buffered data), ``-1`` is returned."
msgstr ""
#: ../Doc/c-api/init.rst:283
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 ""
#: ../Doc/c-api/init.rst:291
msgid ""
"**Bugs and caveats:** The destruction of modules and objects in modules is "
"done in random order; this may cause destructors (:meth:`__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. 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."
msgstr ""
#: ../Doc/c-api/init.rst:307
msgid ""
"This is a backwards-compatible version of :c:func:`Py_FinalizeEx` that "
"disregards the return value."
msgstr ""
#: ../Doc/c-api/init.rst:312
msgid "Process-wide parameters"
msgstr ""
#: ../Doc/c-api/init.rst:322
msgid ""
"This function should be called before :c:func:`Py_Initialize`, if it is "
"called at all. It specifies which encoding and error handling to use with "
"standard IO, with the same meanings as in :func:`str.encode`."
msgstr ""
#: ../Doc/c-api/init.rst:326
msgid ""
"It overrides :envvar:`PYTHONIOENCODING` values, and allows embedding code to "
"control IO encoding when the environment variable does not work."
msgstr ""
#: ../Doc/c-api/init.rst:329
msgid ""
"``encoding`` and/or ``errors`` may be NULL to use :envvar:`PYTHONIOENCODING` "
"and/or default values (depending on other settings)."
msgstr ""
#: ../Doc/c-api/init.rst:333
msgid ""
"Note that :data:`sys.stderr` always uses the \"backslashreplace\" error "
"handler, regardless of this (or any other) setting."
msgstr ""
#: ../Doc/c-api/init.rst:336
msgid ""
"If :c:func:`Py_FinalizeEx` is called, this function will need to be called "
"again in order to affect subsequent calls to :c:func:`Py_Initialize`."
msgstr ""
#: ../Doc/c-api/init.rst:339
msgid ""
"Returns ``0`` if successful, a nonzero value on error (e.g. calling after "
"the interpreter has already been initialized)."
msgstr ""
#: ../Doc/c-api/init.rst:352
msgid ""
"This function should be called before :c:func:`Py_Initialize` is called for "
"the first time, if it is called at all. It tells the interpreter the value "
"of the ``argv[0]`` argument to the :c:func:`main` function of the program "
"(converted to wide characters). This is used by :c:func:`Py_GetPath` and "
"some other functions below to find the Python run-time libraries relative to "
"the interpreter executable. The default value is ``'python'``. The "
"argument should point to a zero-terminated wide character string in static "
"storage whose contents will not change for the duration of the program's "
"execution. No code in the Python interpreter will change the contents of "
"this storage."
msgstr ""
#: ../Doc/c-api/init.rst:363 ../Doc/c-api/init.rst:477
#: ../Doc/c-api/init.rst:579 ../Doc/c-api/init.rst:606
#: ../Doc/c-api/init.rst:623
msgid ""
"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get a :c:type:"
"`wchar_*` string."
msgstr ""
#: ../Doc/c-api/init.rst:371
msgid ""
"Return the program name set with :c:func:`Py_SetProgramName`, or the "
"default. The returned string points into static storage; the caller should "
"not modify its value."
msgstr ""
#: ../Doc/c-api/init.rst:378
msgid ""
"Return the *prefix* for installed platform-independent files. This is "
"derived through a number of complicated rules from the program name set "
"with :c:func:`Py_SetProgramName` and some environment variables; for "
"example, if the program name is ``'/usr/local/bin/python'``, the prefix is "
"``'/usr/local'``. The returned string points into static storage; the caller "
"should not modify its value. This corresponds to the :makevar:`prefix` "
"variable in the top-level :file:`Makefile` and the ``--prefix`` argument to "
"the :program:`configure` script at build time. The value is available to "
"Python code as ``sys.prefix``. It is only useful on Unix. See also the next "
"function."
msgstr ""
#: ../Doc/c-api/init.rst:391
msgid ""
"Return the *exec-prefix* for installed platform-*dependent* files. This is "
"derived through a number of complicated rules from the program name set "
"with :c:func:`Py_SetProgramName` and some environment variables; for "
"example, if the program name is ``'/usr/local/bin/python'``, the exec-prefix "
"is ``'/usr/local'``. The returned string points into static storage; the "
"caller should not modify its value. This corresponds to the :makevar:"
"`exec_prefix` variable in the top-level :file:`Makefile` and the ``--exec-"
"prefix`` argument to the :program:`configure` script at build time. The "
"value is available to Python code as ``sys.exec_prefix``. It is only useful "
"on Unix."
msgstr ""
#: ../Doc/c-api/init.rst:401
msgid ""
"Background: The exec-prefix differs from the prefix when platform dependent "
"files (such as executables and shared libraries) are installed in a "
"different directory tree. In a typical installation, platform dependent "
"files may be installed in the :file:`/usr/local/plat` subtree while platform "
"independent may be installed in :file:`/usr/local`."
msgstr ""
#: ../Doc/c-api/init.rst:407
msgid ""
"Generally speaking, a platform is a combination of hardware and software "
"families, e.g. Sparc machines running the Solaris 2.x operating system are "
"considered the same platform, but Intel machines running Solaris 2.x are "
"another platform, and Intel machines running Linux are yet another "
"platform. Different major revisions of the same operating system generally "
"also form different platforms. Non-Unix operating systems are a different "
"story; the installation strategies on those systems are so different that "
"the prefix and exec-prefix are meaningless, and set to the empty string. "
"Note that compiled Python bytecode files are platform independent (but not "
"independent from the Python version by which they were compiled!)."
msgstr ""
#: ../Doc/c-api/init.rst:418
msgid ""
"System administrators will know how to configure the :program:`mount` or :"
"program:`automount` programs to share :file:`/usr/local` between platforms "
"while having :file:`/usr/local/plat` be a different filesystem for each "
"platform."
msgstr ""
#: ../Doc/c-api/init.rst:430
msgid ""
"Return the full program name of the Python executable; this is computed as "
"a side-effect of deriving the default module search path from the program "
"name (set by :c:func:`Py_SetProgramName` above). The returned string points "
"into static storage; the caller should not modify its value. The value is "
"available to Python code as ``sys.executable``."
msgstr ""
#: ../Doc/c-api/init.rst:444
msgid ""
"Return the default module search path; this is computed from the program "
"name (set by :c:func:`Py_SetProgramName` above) and some environment "
"variables. The returned string consists of a series of directory names "
"separated by a platform dependent delimiter character. The delimiter "
"character is ``':'`` on Unix and Mac OS X, ``';'`` on Windows. The returned "
"string points into static storage; the caller should not modify its value. "
"The list :data:`sys.path` is initialized with this value on interpreter "
"startup; it can be (and usually is) modified later to change the search path "
"for loading modules."
msgstr ""
#: ../Doc/c-api/init.rst:464
msgid ""
"Set the default module search path. If this function is called before :c:"
"func:`Py_Initialize`, then :c:func:`Py_GetPath` won't attempt to compute a "
"default search path but uses the one provided instead. This is useful if "
"Python is embedded by an application that has full knowledge of the location "
"of all modules. The path components should be separated by the platform "
"dependent delimiter character, which is ``':'`` on Unix and Mac OS X, "
"``';'`` on Windows."
msgstr ""
#: ../Doc/c-api/init.rst:472
msgid ""
"This also causes :data:`sys.executable` to be set only to the raw program "
"name (see :c:func:`Py_SetProgramName`) and for :data:`sys.prefix` and :data:"
"`sys.exec_prefix` to be empty. It is up to the caller to modify these if "
"required after calling :c:func:`Py_Initialize`."
msgstr ""
#: ../Doc/c-api/init.rst:480
msgid ""
"The path argument is copied internally, so the caller may free it after the "
"call completes."
msgstr ""
#: ../Doc/c-api/init.rst:486
msgid ""
"Return the version of this Python interpreter. This is a string that looks "
"something like ::"
msgstr ""
#: ../Doc/c-api/init.rst:493
msgid ""
"The first word (up to the first space character) is the current Python "
"version; the first three characters are the major and minor version "
"separated by a period. The returned string points into static storage; the "
"caller should not modify its value. The value is available to Python code "
"as :data:`sys.version`."
msgstr ""
#: ../Doc/c-api/init.rst:503
msgid ""
"Return the platform identifier for the current platform. On Unix, this is "
"formed from the \"official\" name of the operating system, converted to "
"lower case, followed by the major revision number; e.g., for Solaris 2.x, "
"which is also known as SunOS 5.x, the value is ``'sunos5'``. On Mac OS X, "
"it is ``'darwin'``. On Windows, it is ``'win'``. The returned string "
"points into static storage; the caller should not modify its value. The "
"value is available to Python code as ``sys.platform``."
msgstr ""
#: ../Doc/c-api/init.rst:514
msgid ""
"Return the official copyright string for the current Python version, for "
"example"
msgstr ""
#: ../Doc/c-api/init.rst:516
msgid "``'Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam'``"
msgstr ""
#: ../Doc/c-api/init.rst:520
msgid ""
"The returned string points into static storage; the caller should not modify "
"its value. The value is available to Python code as ``sys.copyright``."
msgstr ""
#: ../Doc/c-api/init.rst:526
msgid ""
"Return an indication of the compiler used to build the current Python "
"version, in square brackets, for example::"
msgstr ""
#: ../Doc/c-api/init.rst:533 ../Doc/c-api/init.rst:547
msgid ""
"The returned string points into static storage; the caller should not modify "
"its value. The value is available to Python code as part of the variable "
"``sys.version``."
msgstr ""
#: ../Doc/c-api/init.rst:540
msgid ""
"Return information about the sequence number and build date and time of the "
"current Python interpreter instance, for example ::"
msgstr ""
#: ../Doc/c-api/init.rst:559
msgid ""
"Set :data:`sys.argv` based on *argc* and *argv*. These parameters are "
"similar to those passed to the program's :c:func:`main` function with the "
"difference that the first entry should refer to the script file to be "
"executed rather than the executable hosting the Python interpreter. If "
"there isn't a script that will be run, the first entry in *argv* can be an "
"empty string. If this function fails to initialize :data:`sys.argv`, a "
"fatal condition is signalled using :c:func:`Py_FatalError`."
msgstr ""
#: ../Doc/c-api/init.rst:567
msgid ""
"If *updatepath* is zero, this is all the function does. If *updatepath* is "
"non-zero, the function also modifies :data:`sys.path` according to the "
"following algorithm:"
msgstr ""
#: ../Doc/c-api/init.rst:571
msgid ""
"If the name of an existing script is passed in ``argv[0]``, the absolute "
"path of the directory where the script is located is prepended to :data:`sys."
"path`."
msgstr ""
#: ../Doc/c-api/init.rst:574
msgid ""
"Otherwise (that is, if *argc* is ``0`` or ``argv[0]`` doesn't point to an "
"existing file name), an empty string is prepended to :data:`sys.path`, which "
"is the same as prepending the current working directory (``\".\"``)."
msgstr ""
#: ../Doc/c-api/init.rst:583
msgid ""
"It is recommended that applications embedding the Python interpreter for "
"purposes other than executing a single script pass ``0`` as *updatepath*, "
"and update :data:`sys.path` themselves if desired. See `CVE-2008-5983 "
"<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983>`_."
msgstr ""
#: ../Doc/c-api/init.rst:588
msgid ""
"On versions before 3.1.3, you can achieve the same effect by manually "
"popping the first :data:`sys.path` element after having called :c:func:"
"`PySys_SetArgv`, for example using::"
msgstr ""
#: ../Doc/c-api/init.rst:602
msgid ""
"This function works like :c:func:`PySys_SetArgvEx` with *updatepath* set to "
"``1`` unless the :program:`python` interpreter was started with the :option:"
"`-I`."
msgstr ""
#: ../Doc/c-api/init.rst:609
msgid "The *updatepath* value depends on :option:`-I`."
msgstr ""
#: ../Doc/c-api/init.rst:614
msgid ""
"Set the default \"home\" directory, that is, the location of the standard "
"Python libraries. See :envvar:`PYTHONHOME` for the meaning of the argument "
"string."
msgstr ""
#: ../Doc/c-api/init.rst:618
msgid ""
"The argument should point to a zero-terminated character string in static "
"storage whose contents will not change for the duration of the program's "
"execution. No code in the Python interpreter will change the contents of "
"this storage."
msgstr ""
#: ../Doc/c-api/init.rst:629
msgid ""
"Return the default \"home\", that is, the value set by a previous call to :c:"
"func:`Py_SetPythonHome`, or the value of the :envvar:`PYTHONHOME` "
"environment variable if it is set."
msgstr ""
#: ../Doc/c-api/init.rst:637
msgid "Thread State and the Global Interpreter Lock"
msgstr ""
#: ../Doc/c-api/init.rst:644
msgid ""
"The Python interpreter is not fully thread-safe. In order to support multi-"
"threaded Python programs, there's a global lock, called the :term:`global "
"interpreter lock` or :term:`GIL`, that must be held by the current thread "
"before it can safely access Python objects. Without the lock, even the "
"simplest operations could cause problems in a multi-threaded program: for "
"example, when two threads simultaneously increment the reference count of "
"the same object, the reference count could end up being incremented only "
"once instead of twice."
msgstr ""
#: ../Doc/c-api/init.rst:654
msgid ""
"Therefore, the rule exists that only the thread that has acquired the :term:"
"`GIL` may operate on Python objects or call Python/C API functions. In order "
"to emulate concurrency of execution, the interpreter regularly tries to "
"switch threads (see :func:`sys.setswitchinterval`). The lock is also "
"released around potentially blocking I/O operations like reading or writing "
"a file, so that other Python threads can run in the meantime."
msgstr ""
#: ../Doc/c-api/init.rst:665
msgid ""
"The Python interpreter keeps some thread-specific bookkeeping information "
"inside a data structure called :c:type:`PyThreadState`. There's also one "
"global variable pointing to the current :c:type:`PyThreadState`: it can be "
"retrieved using :c:func:`PyThreadState_Get`."
msgstr ""
#: ../Doc/c-api/init.rst:671
msgid "Releasing the GIL from extension code"
msgstr ""
#: ../Doc/c-api/init.rst:673
msgid ""
"Most extension code manipulating the :term:`GIL` has the following simple "
"structure::"
msgstr ""
#: ../Doc/c-api/init.rst:682
msgid "This is so common that a pair of macros exists to simplify it::"
msgstr ""
#: ../Doc/c-api/init.rst:692
msgid ""
"The :c:macro:`Py_BEGIN_ALLOW_THREADS` macro opens a new block and declares a "
"hidden local variable; the :c:macro:`Py_END_ALLOW_THREADS` macro closes the "
"block."
msgstr ""
#: ../Doc/c-api/init.rst:696
msgid "The block above expands to the following code::"
msgstr ""
#: ../Doc/c-api/init.rst:708
msgid ""
"Here is how these functions work: the global interpreter lock is used to "
"protect the pointer to the current thread state. When releasing the lock "
"and saving the thread state, the current thread state pointer must be "
"retrieved before the lock is released (since another thread could "
"immediately acquire the lock and store its own thread state in the global "
"variable). Conversely, when acquiring the lock and restoring the thread "
"state, the lock must be acquired before storing the thread state pointer."
msgstr ""
#: ../Doc/c-api/init.rst:717
msgid ""
"Calling system I/O functions is the most common use case for releasing the "
"GIL, but it can also be useful before calling long-running computations "
"which don't need access to Python objects, such as compression or "
"cryptographic functions operating over memory buffers. For example, the "
"standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when "
"compressing or hashing data."
msgstr ""
#: ../Doc/c-api/init.rst:728
msgid "Non-Python created threads"
msgstr ""
#: ../Doc/c-api/init.rst:730
msgid ""
"When threads are created using the dedicated Python APIs (such as the :mod:"
"`threading` module), a thread state is automatically associated to them and "
"the code showed above is therefore correct. However, when threads are "
"created from C (for example by a third-party library with its own thread "
"management), they don't hold the GIL, nor is there a thread state structure "
"for them."
msgstr ""
#: ../Doc/c-api/init.rst:737
msgid ""
"If you need to call Python code from these threads (often this will be part "
"of a callback API provided by the aforementioned third-party library), you "
"must first register these threads with the interpreter by creating a thread "
"state data structure, then acquiring the GIL, and finally storing their "
"thread state pointer, before you can start using the Python/C API. When you "
"are done, you should reset the thread state pointer, release the GIL, and "
"finally free the thread state data structure."
msgstr ""
#: ../Doc/c-api/init.rst:745
msgid ""
"The :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release` functions "
"do all of the above automatically. The typical idiom for calling into "
"Python from a C thread is::"
msgstr ""
#: ../Doc/c-api/init.rst:759
msgid ""
"Note that the :c:func:`PyGILState_\\*` functions assume there is only one "
"global interpreter (created automatically by :c:func:`Py_Initialize`). "
"Python supports the creation of additional interpreters (using :c:func:"
"`Py_NewInterpreter`), but mixing multiple interpreters and the :c:func:"
"`PyGILState_\\*` API is unsupported."
msgstr ""
#: ../Doc/c-api/init.rst:765
msgid ""
"Another important thing to note about threads is their behaviour in the face "
"of the C :c:func:`fork` call. On most systems with :c:func:`fork`, after a "
"process forks only the thread that issued the fork will exist. That also "
"means any locks held by other threads will never be released. Python solves "
"this for :func:`os.fork` by acquiring the locks it uses internally before "
"the fork, and releasing them afterwards. In addition, it resets any :ref:"
"`lock-objects` in the child. When extending or embedding Python, there is no "
"way to inform Python of additional (non-Python) locks that need to be "
"acquired before or reset after a fork. OS facilities such as :c:func:"
"`pthread_atfork` would need to be used to accomplish the same thing. "
"Additionally, when extending or embedding Python, calling :c:func:`fork` "
"directly rather than through :func:`os.fork` (and returning to or calling "
"into Python) may result in a deadlock by one of Python's internal locks "
"being held by a thread that is defunct after the fork. :c:func:"
"`PyOS_AfterFork_Child` tries to reset the necessary locks, but is not always "
"able to."
msgstr ""
#: ../Doc/c-api/init.rst:784
msgid "High-level API"
msgstr ""
#: ../Doc/c-api/init.rst:786
msgid ""
"These are the most commonly used types and functions when writing C "
"extension code, or when embedding the Python interpreter:"
msgstr ""
#: ../Doc/c-api/init.rst:791
msgid ""
"This data structure represents the state shared by a number of cooperating "
"threads. Threads belonging to the same interpreter share their module "
"administration and a few other internal items. There are no public members "
"in this structure."
msgstr ""
#: ../Doc/c-api/init.rst:796
msgid ""
"Threads belonging to different interpreters initially share nothing, except "
"process state like available memory, open file descriptors and such. The "
"global interpreter lock is also shared by all threads, regardless of to "
"which interpreter they belong."
msgstr ""
#: ../Doc/c-api/init.rst:804
msgid ""
"This data structure represents the state of a single thread. The only "
"public data member is :c:type:`PyInterpreterState \\*`:attr:`interp`, which "
"points to this thread's interpreter state."
msgstr ""
#: ../Doc/c-api/init.rst:817
msgid ""
"Initialize and acquire the global interpreter lock. It should be called in "
"the main thread before creating a second thread or engaging in any other "
"thread operations such as ``PyEval_ReleaseThread(tstate)``. It is not needed "
"before calling :c:func:`PyEval_SaveThread` or :c:func:`PyEval_RestoreThread`."
msgstr ""
#: ../Doc/c-api/init.rst:822
msgid "This is a no-op when called for a second time."
msgstr ""
#: ../Doc/c-api/init.rst:824
msgid ""
"This function is now called by :c:func:`Py_Initialize()`, so you don't have "
"to call it yourself anymore."
msgstr ""
#: ../Doc/c-api/init.rst:828
msgid ""
"This function cannot be called before :c:func:`Py_Initialize()` anymore."
msgstr ""
#: ../Doc/c-api/init.rst:836
msgid ""
"Returns a non-zero value if :c:func:`PyEval_InitThreads` has been called. "
"This function can be called without holding the GIL, and therefore can be "
"used to avoid calls to the locking API when running single-threaded."
msgstr ""
#: ../Doc/c-api/init.rst:840
msgid "The :term:`GIL` is now initialized by :c:func:`Py_Initialize()`."
msgstr ""
#: ../Doc/c-api/init.rst:846
msgid ""
"Release the global interpreter lock (if it has been created and thread "
"support is enabled) and reset the thread state to *NULL*, returning the "
"previous thread state (which is not *NULL*). If the lock has been created, "
"the current thread must have acquired it."
msgstr ""
#: ../Doc/c-api/init.rst:854
msgid ""
"Acquire the global interpreter lock (if it has been created and thread "
"support is enabled) and set the thread state to *tstate*, which must not be "
"*NULL*. If the lock has been created, the current thread must not have "
"acquired it, otherwise deadlock ensues."
msgstr ""
#: ../Doc/c-api/init.rst:860 ../Doc/c-api/init.rst:913
msgid ""
"Calling this function from a thread when the runtime is finalizing will "
"terminate the thread, even if the thread was not created by Python. You can "
"use :c:func:`_Py_IsFinalizing` or :func:`sys.is_finalizing` to check if the "
"interpreter is in process of being finalized before calling this function to "
"avoid unwanted termination."
msgstr ""
#: ../Doc/c-api/init.rst:868
msgid ""
"Return the current thread state. The global interpreter lock must be held. "
"When the current thread state is *NULL*, this issues a fatal error (so that "
"the caller needn't check for *NULL*)."
msgstr ""
#: ../Doc/c-api/init.rst:875
msgid ""
"Swap the current thread state with the thread state given by the argument "
"*tstate*, which may be *NULL*. The global interpreter lock must be held and "
"is not released."
msgstr ""
#: ../Doc/c-api/init.rst:882
msgid ""
"This function is called from :c:func:`PyOS_AfterFork_Child` to ensure that "
"newly created child processes don't hold locks referring to threads which "
"are not running in the child process."
msgstr ""
#: ../Doc/c-api/init.rst:887
msgid ""
"The following functions use thread-local storage, and are not compatible "
"with sub-interpreters:"
msgstr ""
#: ../Doc/c-api/init.rst:892
msgid ""
"Ensure that the current thread is ready to call the Python C API regardless "
"of the current state of Python, or of the global interpreter lock. This may "
"be called as many times as desired by a thread as long as each call is "
"matched with a call to :c:func:`PyGILState_Release`. In general, other "
"thread-related APIs may be used between :c:func:`PyGILState_Ensure` and :c:"
"func:`PyGILState_Release` calls as long as the thread state is restored to "
"its previous state before the Release(). For example, normal usage of the :"
"c:macro:`Py_BEGIN_ALLOW_THREADS` and :c:macro:`Py_END_ALLOW_THREADS` macros "
"is acceptable."
msgstr ""
#: ../Doc/c-api/init.rst:902
msgid ""
"The return value is an opaque \"handle\" to the thread state when :c:func:"
"`PyGILState_Ensure` was called, and must be passed to :c:func:"
"`PyGILState_Release` to ensure Python is left in the same state. Even though "
"recursive calls are allowed, these handles *cannot* be shared - each unique "
"call to :c:func:`PyGILState_Ensure` must save the handle for its call to :c:"
"func:`PyGILState_Release`."
msgstr ""
#: ../Doc/c-api/init.rst:909
msgid ""
"When the function returns, the current thread will hold the GIL and be able "
"to call arbitrary Python code. Failure is a fatal error."
msgstr ""
#: ../Doc/c-api/init.rst:921
msgid ""
"Release any resources previously acquired. After this call, Python's state "
"will be the same as it was prior to the corresponding :c:func:"
"`PyGILState_Ensure` call (but generally this state will be unknown to the "
"caller, hence the use of the GILState API)."
msgstr ""
#: ../Doc/c-api/init.rst:926
msgid ""
"Every call to :c:func:`PyGILState_Ensure` must be matched by a call to :c:"
"func:`PyGILState_Release` on the same thread."
msgstr ""
#: ../Doc/c-api/init.rst:932
msgid ""
"Get the current thread state for this thread. May return ``NULL`` if no "
"GILState API has been used on the current thread. Note that the main thread "
"always has such a thread-state, even if no auto-thread-state call has been "
"made on the main thread. This is mainly a helper/diagnostic function."
msgstr ""
#: ../Doc/c-api/init.rst:940
msgid ""
"Return ``1`` if the current thread is holding the GIL and ``0`` otherwise. "
"This function can be called from any thread at any time. Only if it has had "
"its Python thread state initialized and currently is holding the GIL will it "
"return ``1``. This is mainly a helper/diagnostic function. It can be useful "
"for example in callback contexts or memory allocation functions when knowing "
"that the GIL is locked can allow the caller to perform sensitive actions or "
"otherwise behave differently."
msgstr ""
#: ../Doc/c-api/init.rst:952
msgid ""
"The following macros are normally used without a trailing semicolon; look "
"for example usage in the Python source distribution."
msgstr ""
#: ../Doc/c-api/init.rst:958
msgid ""
"This macro expands to ``{ PyThreadState *_save; _save = PyEval_SaveThread();"
"``. Note that it contains an opening brace; it must be matched with a "
"following :c:macro:`Py_END_ALLOW_THREADS` macro. See above for further "
"discussion of this macro."
msgstr ""
#: ../Doc/c-api/init.rst:966
msgid ""
"This macro expands to ``PyEval_RestoreThread(_save); }``. Note that it "
"contains a closing brace; it must be matched with an earlier :c:macro:"
"`Py_BEGIN_ALLOW_THREADS` macro. See above for further discussion of this "
"macro."
msgstr ""
#: ../Doc/c-api/init.rst:974
msgid ""
"This macro expands to ``PyEval_RestoreThread(_save);``: it is equivalent to :"
"c:macro:`Py_END_ALLOW_THREADS` without the closing brace."
msgstr ""
#: ../Doc/c-api/init.rst:980
msgid ""
"This macro expands to ``_save = PyEval_SaveThread();``: it is equivalent to :"
"c:macro:`Py_BEGIN_ALLOW_THREADS` without the opening brace and variable "
"declaration."
msgstr ""
#: ../Doc/c-api/init.rst:986
msgid "Low-level API"
msgstr ""
#: ../Doc/c-api/init.rst:988
msgid ""
"All of the following functions must be called after :c:func:`Py_Initialize`."
msgstr ""
#: ../Doc/c-api/init.rst:990
msgid ":c:func:`Py_Initialize()` now initializes the :term:`GIL`."
msgstr ""
#: ../Doc/c-api/init.rst:996
msgid ""
"Create a new interpreter state object. The global interpreter lock need not "
"be held, but may be held if it is necessary to serialize calls to this "
"function."
msgstr ""
#: ../Doc/c-api/init.rst:1003
msgid ""
"Reset all information in an interpreter state object. The global "
"interpreter lock must be held."
msgstr ""
#: ../Doc/c-api/init.rst:1009
msgid ""
"Destroy an interpreter state object. The global interpreter lock need not "
"be held. The interpreter state must have been reset with a previous call "
"to :c:func:`PyInterpreterState_Clear`."
msgstr ""
#: ../Doc/c-api/init.rst:1016
msgid ""
"Create a new thread state object belonging to the given interpreter object. "
"The global interpreter lock need not be held, but may be held if it is "
"necessary to serialize calls to this function."
msgstr ""
#: ../Doc/c-api/init.rst:1023
msgid ""
"Reset all information in a thread state object. The global interpreter lock "
"must be held."
msgstr ""
#: ../Doc/c-api/init.rst:1029
msgid ""
"Destroy a thread state object. The global interpreter lock need not be "
"held. The thread state must have been reset with a previous call to :c:func:"
"`PyThreadState_Clear`."
msgstr ""
#: ../Doc/c-api/init.rst:1036
msgid ""
"Return the interpreter's unique ID. If there was any error in doing so then "
"``-1`` is returned and an error is set."
msgstr ""
#: ../Doc/c-api/init.rst:1044
msgid ""
"Return a dictionary in which extensions can store thread-specific state "
"information. Each extension should use a unique key to use to store state "
"in the dictionary. It is okay to call this function when no current thread "
"state is available. If this function returns *NULL*, no exception has been "
"raised and the caller should assume no current thread state is available."
msgstr ""
#: ../Doc/c-api/init.rst:1053
msgid ""
"Asynchronously raise an exception in a thread. The *id* argument is the "
"thread id of the target thread; *exc* is the exception object to be raised. "
"This function does not steal any references to *exc*. To prevent naive "
"misuse, you must write your own C extension to call this. Must be called "
"with the GIL held. Returns the number of thread states modified; this is "
"normally one, but will be zero if the thread id isn't found. If *exc* is :"
"const:`NULL`, the pending exception (if any) for the thread is cleared. This "
"raises no exceptions."
msgstr ""
#: ../Doc/c-api/init.rst:1061
msgid ""
"The type of the *id* parameter changed from :c:type:`long` to :c:type:"
"`unsigned long`."
msgstr ""
#: ../Doc/c-api/init.rst:1067
msgid ""
"Acquire the global interpreter lock and set the current thread state to "
"*tstate*, which should not be *NULL*. The lock must have been created "
"earlier. If this thread already has the lock, deadlock ensues."
msgstr ""
#: ../Doc/c-api/init.rst:1071
msgid ""
":c:func:`PyEval_RestoreThread` is a higher-level function which is always "
"available (even when threads have not been initialized)."
msgstr ""
#: ../Doc/c-api/init.rst:1077
msgid ""
"Reset the current thread state to *NULL* and release the global interpreter "
"lock. The lock must have been created earlier and must be held by the "
"current thread. The *tstate* argument, which must not be *NULL*, is only "
"used to check that it represents the current thread state --- if it isn't, a "
"fatal error is reported."
msgstr ""
#: ../Doc/c-api/init.rst:1083
msgid ""
":c:func:`PyEval_SaveThread` is a higher-level function which is always "
"available (even when threads have not been initialized)."
msgstr ""
#: ../Doc/c-api/init.rst:1089
msgid ""
"Acquire the global interpreter lock. The lock must have been created "
"earlier. If this thread already has the lock, a deadlock ensues."
msgstr ""
#: ../Doc/c-api/init.rst:1092
msgid ""
"This function does not update the current thread state. Please use :c:func:"
"`PyEval_RestoreThread` or :c:func:`PyEval_AcquireThread` instead."
msgstr ""
#: ../Doc/c-api/init.rst:1100
msgid ""
"Release the global interpreter lock. The lock must have been created "
"earlier."
msgstr ""
#: ../Doc/c-api/init.rst:1102
msgid ""
"This function does not update the current thread state. Please use :c:func:"
"`PyEval_SaveThread` or :c:func:`PyEval_ReleaseThread` instead."
msgstr ""
#: ../Doc/c-api/init.rst:1111
msgid "Sub-interpreter support"
msgstr ""
#: ../Doc/c-api/init.rst:1113
msgid ""
"While in most uses, you will only embed a single Python interpreter, there "
"are cases where you need to create several independent interpreters in the "
"same process and perhaps even in the same thread. Sub-interpreters allow "
"you to do that. You can switch between sub-interpreters using the :c:func:"
"`PyThreadState_Swap` function. You can create and destroy them using the "
"following functions:"
msgstr ""
#: ../Doc/c-api/init.rst:1131
msgid ""
"Create a new sub-interpreter. This is an (almost) totally separate "
"environment for the execution of Python code. In particular, the new "
"interpreter has separate, independent versions of all imported modules, "
"including the fundamental modules :mod:`builtins`, :mod:`__main__` and :mod:"
"`sys`. The table of loaded modules (``sys.modules``) and the module search "
"path (``sys.path``) are also separate. The new environment has no ``sys."
"argv`` variable. It has new standard I/O stream file objects ``sys.stdin``, "
"``sys.stdout`` and ``sys.stderr`` (however these refer to the same "
"underlying file descriptors)."
msgstr ""
#: ../Doc/c-api/init.rst:1141
msgid ""
"The return value points to the first thread state created in the new sub-"
"interpreter. This thread state is made in the current thread state. Note "
"that no actual thread is created; see the discussion of thread states "
"below. If creation of the new interpreter is unsuccessful, *NULL* is "
"returned; no exception is set since the exception state is stored in the "
"current thread state and there may not be a current thread state. (Like all "
"other Python/C API functions, the global interpreter lock must be held "
"before calling this function and is still held when it returns; however, "
"unlike most other Python/C API functions, there needn't be a current thread "
"state on entry.)"
msgstr ""
#: ../Doc/c-api/init.rst:1156
msgid ""
"Extension modules are shared between (sub-)interpreters as follows: the "
"first time a particular extension is imported, it is initialized normally, "
"and a (shallow) copy of its module's dictionary is squirreled away. When "
"the same extension is imported by another (sub-)interpreter, a new module is "
"initialized and filled with the contents of this copy; the extension's "
"``init`` function is not called. Note that this is different from what "
"happens when an extension is imported after the interpreter has been "
"completely re-initialized by calling :c:func:`Py_FinalizeEx` and :c:func:"
"`Py_Initialize`; in that case, the extension's ``initmodule`` function *is* "
"called again."
msgstr ""
#: ../Doc/c-api/init.rst:1173
msgid ""
"Destroy the (sub-)interpreter represented by the given thread state. The "
"given thread state must be the current thread state. See the discussion of "
"thread states below. When the call returns, the current thread state is "
"*NULL*. All thread states associated with this interpreter are destroyed. "
"(The global interpreter lock must be held before calling this function and "
"is still held when it returns.) :c:func:`Py_FinalizeEx` will destroy all "
"sub-interpreters that haven't been explicitly destroyed at that point."
msgstr ""
#: ../Doc/c-api/init.rst:1183
msgid "Bugs and caveats"
msgstr ""
#: ../Doc/c-api/init.rst:1185
msgid ""
"Because sub-interpreters (and the main interpreter) are part of the same "
"process, the insulation between them isn't perfect --- for example, using "
"low-level file operations like :func:`os.close` they can (accidentally or "
"maliciously) affect each other's open files. Because of the way extensions "
"are shared between (sub-)interpreters, some extensions may not work "
"properly; this is especially likely when the extension makes use of (static) "
"global variables, or when the extension manipulates its module's dictionary "
"after its initialization. It is possible to insert objects created in one "
"sub-interpreter into a namespace of another sub-interpreter; this should be "
"done with great care to avoid sharing user-defined functions, methods, "
"instances or classes between sub-interpreters, since import operations "
"executed by such objects may affect the wrong (sub-)interpreter's dictionary "
"of loaded modules."
msgstr ""
#: ../Doc/c-api/init.rst:1199
msgid ""
"Also note that combining this functionality with :c:func:`PyGILState_\\*` "
"APIs is delicate, because these APIs assume a bijection between Python "
"thread states and OS-level threads, an assumption broken by the presence of "
"sub-interpreters. It is highly recommended that you don't switch sub-"
"interpreters between a pair of matching :c:func:`PyGILState_Ensure` and :c:"
"func:`PyGILState_Release` calls. Furthermore, extensions (such as :mod:"
"`ctypes`) using these APIs to allow calling of Python code from non-Python "
"created threads will probably be broken when using sub-interpreters."
msgstr ""
#: ../Doc/c-api/init.rst:1210
msgid "Asynchronous Notifications"
msgstr ""
#: ../Doc/c-api/init.rst:1212
msgid ""
"A mechanism is provided to make asynchronous notifications to the main "
"interpreter thread. These notifications take the form of a function pointer "
"and a void pointer argument."
msgstr ""
#: ../Doc/c-api/init.rst:1221
msgid ""
"Schedule a function to be called from the main interpreter thread. On "
"success, ``0`` is returned and *func* is queued for being called in the main "
"thread. On failure, ``-1`` is returned without setting any exception."
msgstr ""
#: ../Doc/c-api/init.rst:1225
msgid ""
"When successfully queued, *func* will be *eventually* called from the main "
"interpreter thread with the argument *arg*. It will be called "
"asynchronously with respect to normally running Python code, but with both "
"these conditions met:"
msgstr ""
#: ../Doc/c-api/init.rst:1230
msgid "on a :term:`bytecode` boundary;"
msgstr ""
#: ../Doc/c-api/init.rst:1231
msgid ""
"with the main thread holding the :term:`global interpreter lock` (*func* can "
"therefore use the full C API)."
msgstr ""
#: ../Doc/c-api/init.rst:1234
msgid ""
"*func* must return ``0`` on success, or ``-1`` on failure with an exception "
"set. *func* won't be interrupted to perform another asynchronous "
"notification recursively, but it can still be interrupted to switch threads "
"if the global interpreter lock is released."
msgstr ""
#: ../Doc/c-api/init.rst:1239
msgid ""
"This function doesn't need a current thread state to run, and it doesn't "
"need the global interpreter lock."
msgstr ""
#: ../Doc/c-api/init.rst:1243
msgid ""
"This is a low-level function, only useful for very special cases. There is "
"no guarantee that *func* will be called as quick as possible. If the main "
"thread is busy executing a system call, *func* won't be called before the "
"system call returns. This function is generally **not** suitable for "
"calling Python code from arbitrary C threads. Instead, use the :ref:"
"`PyGILState API<gilstate>`."
msgstr ""
#: ../Doc/c-api/init.rst:1255
msgid "Profiling and Tracing"
msgstr ""
#: ../Doc/c-api/init.rst:1260
msgid ""
"The Python interpreter provides some low-level support for attaching "
"profiling and execution tracing facilities. These are used for profiling, "
"debugging, and coverage analysis tools."
msgstr ""
#: ../Doc/c-api/init.rst:1264
msgid ""
"This C interface allows the profiling or tracing code to avoid the overhead "
"of calling through Python-level callable objects, making a direct C function "
"call instead. The essential attributes of the facility have not changed; "
"the interface allows trace functions to be installed per-thread, and the "
"basic events reported to the trace function are the same as had been "
"reported to the Python-level trace functions in previous versions."
msgstr ""
#: ../Doc/c-api/init.rst:1274
msgid ""
"The type of the trace function registered using :c:func:`PyEval_SetProfile` "
"and :c:func:`PyEval_SetTrace`. The first parameter is the object passed to "
"the registration function as *obj*, *frame* is the frame object to which the "
"event pertains, *what* is one of the constants :const:`PyTrace_CALL`, :const:"
"`PyTrace_EXCEPTION`, :const:`PyTrace_LINE`, :const:`PyTrace_RETURN`, :const:"
"`PyTrace_C_CALL`, :const:`PyTrace_C_EXCEPTION`, :const:`PyTrace_C_RETURN`, "
"or :const:`PyTrace_OPCODE`, and *arg* depends on the value of *what*:"
msgstr ""
#: ../Doc/c-api/init.rst:1283
msgid "Value of *what*"
msgstr ""
#: ../Doc/c-api/init.rst:1283
msgid "Meaning of *arg*"
msgstr ""
#: ../Doc/c-api/init.rst:1285
msgid ":const:`PyTrace_CALL`"
msgstr ""
#: ../Doc/c-api/init.rst:1285 ../Doc/c-api/init.rst:1290
#: ../Doc/c-api/init.rst:1301
msgid "Always :c:data:`Py_None`."
msgstr ""
#: ../Doc/c-api/init.rst:1287
msgid ":const:`PyTrace_EXCEPTION`"
msgstr ""
#: ../Doc/c-api/init.rst:1287
msgid "Exception information as returned by :func:`sys.exc_info`."
msgstr ""
#: ../Doc/c-api/init.rst:1290
msgid ":const:`PyTrace_LINE`"
msgstr ""
#: ../Doc/c-api/init.rst:1292
msgid ":const:`PyTrace_RETURN`"
msgstr ""
#: ../Doc/c-api/init.rst:1292
msgid ""
"Value being returned to the caller, or *NULL* if caused by an exception."
msgstr ""
#: ../Doc/c-api/init.rst:1295
msgid ":const:`PyTrace_C_CALL`"
msgstr ""
#: ../Doc/c-api/init.rst:1295 ../Doc/c-api/init.rst:1297
#: ../Doc/c-api/init.rst:1299
msgid "Function object being called."
msgstr ""
#: ../Doc/c-api/init.rst:1297
msgid ":const:`PyTrace_C_EXCEPTION`"
msgstr ""
#: ../Doc/c-api/init.rst:1299
msgid ":const:`PyTrace_C_RETURN`"
msgstr ""
#: ../Doc/c-api/init.rst:1301
msgid ":const:`PyTrace_OPCODE`"
msgstr ""
#: ../Doc/c-api/init.rst:1306
msgid ""
"The value of the *what* parameter to a :c:type:`Py_tracefunc` function when "
"a new call to a function or method is being reported, or a new entry into a "
"generator. Note that the creation of the iterator for a generator function "
"is not reported as there is no control transfer to the Python bytecode in "
"the corresponding frame."
msgstr ""
#: ../Doc/c-api/init.rst:1315
msgid ""
"The value of the *what* parameter to a :c:type:`Py_tracefunc` function when "
"an exception has been raised. The callback function is called with this "
"value for *what* when after any bytecode is processed after which the "
"exception becomes set within the frame being executed. The effect of this "
"is that as exception propagation causes the Python stack to unwind, the "
"callback is called upon return to each frame as the exception propagates. "
"Only trace functions receives these events; they are not needed by the "
"profiler."
msgstr ""
#: ../Doc/c-api/init.rst:1326
msgid ""
"The value passed as the *what* parameter to a :c:type:`Py_tracefunc` "
"function (but not a profiling function) when a line-number event is being "
"reported. It may be disabled for a frame by setting :attr:`f_trace_lines` to "
"*0* on that frame."
msgstr ""
#: ../Doc/c-api/init.rst:1333
msgid ""
"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when "
"a call is about to return."
msgstr ""
#: ../Doc/c-api/init.rst:1339
msgid ""
"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when "
"a C function is about to be called."
msgstr ""
#: ../Doc/c-api/init.rst:1345
msgid ""
"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when "
"a C function has raised an exception."
msgstr ""
#: ../Doc/c-api/init.rst:1351
msgid ""
"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when "
"a C function has returned."
msgstr ""
#: ../Doc/c-api/init.rst:1357
msgid ""
"The value for the *what* parameter to :c:type:`Py_tracefunc` functions (but "
"not profiling functions) when a new opcode is about to be executed. This "
"event is not emitted by default: it must be explicitly requested by setting :"
"attr:`f_trace_opcodes` to *1* on the frame."
msgstr ""
#: ../Doc/c-api/init.rst:1365
msgid ""
"Set the profiler function to *func*. The *obj* parameter is passed to the "
"function as its first parameter, and may be any Python object, or *NULL*. "
"If the profile function needs to maintain state, using a different value for "
"*obj* for each thread provides a convenient and thread-safe place to store "
"it. The profile function is called for all monitored events except :const:"
"`PyTrace_LINE` :const:`PyTrace_OPCODE` and :const:`PyTrace_EXCEPTION`."
msgstr ""
#: ../Doc/c-api/init.rst:1375
msgid ""
"Set the tracing function to *func*. This is similar to :c:func:"
"`PyEval_SetProfile`, except the tracing function does receive line-number "
"events and per-opcode events, but does not receive any event related to C "
"function objects being called. Any trace function registered using :c:func:"
"`PyEval_SetTrace` will not receive :const:`PyTrace_C_CALL`, :const:"
"`PyTrace_C_EXCEPTION` or :const:`PyTrace_C_RETURN` as a value for the *what* "
"parameter."
msgstr ""
#: ../Doc/c-api/init.rst:1385
msgid "Advanced Debugger Support"
msgstr "Support avancé du débogueur"
#: ../Doc/c-api/init.rst:1390
msgid ""
"These functions are only intended to be used by advanced debugging tools."
msgstr ""
#: ../Doc/c-api/init.rst:1395
msgid ""
"Return the interpreter state object at the head of the list of all such "
"objects."
msgstr ""
#: ../Doc/c-api/init.rst:1400
msgid "Return the main interpreter state object."
msgstr ""
#: ../Doc/c-api/init.rst:1405
msgid ""
"Return the next interpreter state object after *interp* from the list of all "
"such objects."
msgstr ""
#: ../Doc/c-api/init.rst:1411
msgid ""
"Return the pointer to the first :c:type:`PyThreadState` object in the list "
"of threads associated with the interpreter *interp*."
msgstr ""
#: ../Doc/c-api/init.rst:1417
msgid ""
"Return the next thread state object after *tstate* from the list of all such "
"objects belonging to the same :c:type:`PyInterpreterState` object."
msgstr ""
#: ../Doc/c-api/init.rst:1424
msgid "Thread Local Storage Support"
msgstr ""
#: ../Doc/c-api/init.rst:1428
msgid ""
"The Python interpreter provides low-level support for thread-local storage "
"(TLS) which wraps the underlying native TLS implementation to support the "
"Python-level thread local storage API (:class:`threading.local`). The "
"CPython C level APIs are similar to those offered by pthreads and Windows: "
"use a thread key and functions to associate a :c:type:`void\\*` value per "
"thread."
msgstr ""
#: ../Doc/c-api/init.rst:1435
msgid ""
"The GIL does *not* need to be held when calling these functions; they supply "
"their own locking."
msgstr ""
#: ../Doc/c-api/init.rst:1438
msgid ""
"Note that :file:`Python.h` does not include the declaration of the TLS APIs, "
"you need to include :file:`pythread.h` to use thread-local storage."
msgstr ""
#: ../Doc/c-api/init.rst:1442
msgid ""
"None of these API functions handle memory management on behalf of the :c:"
"type:`void\\*` values. You need to allocate and deallocate them yourself. "
"If the :c:type:`void\\*` values happen to be :c:type:`PyObject\\*`, these "
"functions don't do refcount operations on them either."
msgstr ""
#: ../Doc/c-api/init.rst:1450
msgid "Thread Specific Storage (TSS) API"
msgstr ""
#: ../Doc/c-api/init.rst:1452
msgid ""
"TSS API is introduced to supersede the use of the existing TLS API within "
"the CPython interpreter. This API uses a new type :c:type:`Py_tss_t` "
"instead of :c:type:`int` to represent thread keys."
msgstr ""
#: ../Doc/c-api/init.rst:1458
msgid "\"A New C-API for Thread-Local Storage in CPython\" (:pep:`539`)"
msgstr ""
#: ../Doc/c-api/init.rst:1463
msgid ""
"This data structure represents the state of a thread key, the definition of "
"which may depend on the underlying TLS implementation, and it has an "
"internal field representing the key's initialization state. There are no "
"public members in this structure."
msgstr ""
#: ../Doc/c-api/init.rst:1468
msgid ""
"When :ref:`Py_LIMITED_API <stable>` is not defined, static allocation of "
"this type by :c:macro:`Py_tss_NEEDS_INIT` is allowed."
msgstr ""
#: ../Doc/c-api/init.rst:1474
msgid ""
"This macro expands to the initializer for :c:type:`Py_tss_t` variables. Note "
"that this macro won't be defined with :ref:`Py_LIMITED_API <stable>`."
msgstr ""
#: ../Doc/c-api/init.rst:1479
msgid "Dynamic Allocation"
msgstr ""
#: ../Doc/c-api/init.rst:1481
msgid ""
"Dynamic allocation of the :c:type:`Py_tss_t`, required in extension modules "
"built with :ref:`Py_LIMITED_API <stable>`, where static allocation of this "
"type is not possible due to its implementation being opaque at build time."
msgstr ""
#: ../Doc/c-api/init.rst:1488
msgid ""
"Return a value which is the same state as a value initialized with :c:macro:"
"`Py_tss_NEEDS_INIT`, or *NULL* in the case of dynamic allocation failure."
msgstr ""
#: ../Doc/c-api/init.rst:1495
msgid ""
"Free the given *key* allocated by :c:func:`PyThread_tss_alloc`, after first "
"calling :c:func:`PyThread_tss_delete` to ensure any associated thread locals "
"have been unassigned. This is a no-op if the *key* argument is `NULL`."
msgstr ""
#: ../Doc/c-api/init.rst:1501
msgid ""
"A freed key becomes a dangling pointer, you should reset the key to `NULL`."
msgstr ""
#: ../Doc/c-api/init.rst:1506
msgid "Methods"
msgstr "Méthodes"
#: ../Doc/c-api/init.rst:1508
msgid ""
"The parameter *key* of these functions must not be *NULL*. Moreover, the "
"behaviors of :c:func:`PyThread_tss_set` and :c:func:`PyThread_tss_get` are "
"undefined if the given :c:type:`Py_tss_t` has not been initialized by :c:"
"func:`PyThread_tss_create`."
msgstr ""
#: ../Doc/c-api/init.rst:1516
msgid ""
"Return a non-zero value if the given :c:type:`Py_tss_t` has been initialized "
"by :c:func:`PyThread_tss_create`."
msgstr ""
#: ../Doc/c-api/init.rst:1522
msgid ""
"Return a zero value on successful initialization of a TSS key. The behavior "
"is undefined if the value pointed to by the *key* argument is not "
"initialized by :c:macro:`Py_tss_NEEDS_INIT`. This function can be called "
"repeatedly on the same key -- calling it on an already initialized key is a "
"no-op and immediately returns success."
msgstr ""
#: ../Doc/c-api/init.rst:1531
msgid ""
"Destroy a TSS key to forget the values associated with the key across all "
"threads, and change the key's initialization state to uninitialized. A "
"destroyed key is able to be initialized again by :c:func:"
"`PyThread_tss_create`. This function can be called repeatedly on the same "
"key -- calling it on an already destroyed key is a no-op."
msgstr ""
#: ../Doc/c-api/init.rst:1540
msgid ""
"Return a zero value to indicate successfully associating a :c:type:`void\\*` "
"value with a TSS key in the current thread. Each thread has a distinct "
"mapping of the key to a :c:type:`void\\*` value."
msgstr ""
#: ../Doc/c-api/init.rst:1547
msgid ""
"Return the :c:type:`void\\*` value associated with a TSS key in the current "
"thread. This returns *NULL* if no value is associated with the key in the "
"current thread."
msgstr ""
#: ../Doc/c-api/init.rst:1555
msgid "Thread Local Storage (TLS) API"
msgstr ""
#: ../Doc/c-api/init.rst:1557
msgid ""
"This API is superseded by :ref:`Thread Specific Storage (TSS) API <thread-"
"specific-storage-api>`."
msgstr ""
#: ../Doc/c-api/init.rst:1562
msgid ""
"This version of the API does not support platforms where the native TLS key "
"is defined in a way that cannot be safely cast to ``int``. On such "
"platforms, :c:func:`PyThread_create_key` will return immediately with a "
"failure status, and the other TLS functions will all be no-ops on such "
"platforms."
msgstr ""
#: ../Doc/c-api/init.rst:1567
msgid ""
"Due to the compatibility problem noted above, this version of the API should "
"not be used in new code."
msgstr ""
#~ msgid "Name"
#~ msgstr "Nom"
#~ msgid "Value"
#~ msgstr "Valeur"
#~ msgid "0"
#~ msgstr "0"
#~ msgid "1"
#~ msgstr "1"
#~ msgid "2"
#~ msgstr "2"
#~ msgid "3"
#~ msgstr "3"
#~ msgid "4"
#~ msgstr "4"
#~ msgid "5"
#~ msgstr "5"
#~ msgid "6"
#~ msgstr "6"
#~ msgid "7"
#~ msgstr "7"
#~ msgid "8"
#~ msgstr "8"
#~ msgid "10"
#~ msgstr "10"
View Git Blame Copy Permalink