# SOME DESCRIPTIVE TITLE.

# Copyright (C) 2001 Python Software Foundation

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

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

#

# Translators:

# python-doc bot, 2025

#

#, fuzzy

msgid ""

msgstr ""

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

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

"POT-Creation-Date: 2026-06-17 16:52+0000\n"

"PO-Revision-Date: 2025-09-16 00:00+0000\n"

"Last-Translator: python-doc bot, 2025\n"

"Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"

"id/)\n"

"MIME-Version: 1.0\n"

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

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

"Language: id\n"

"Plural-Forms: nplurals=1; plural=0;\n"

msgid "Module Objects"

msgstr ""

msgid ""

"This instance of :c:type:`PyTypeObject` represents the Python module type. "

"This is exposed to Python programs as :py:class:`types.ModuleType`."

msgstr ""

msgid ""

"Return true if *p* is a module object, or a subtype of a module object. This "

"function always succeeds."

msgstr ""

msgid ""

"Return true if *p* is a module object, but not a subtype of :c:data:"

"`PyModule_Type`. This function always succeeds."

msgstr ""

msgid ""

"Return a new module object with :attr:`module.__name__` set to *name*. The "

"module's :attr:`!__name__`, :attr:`~module.__doc__`, :attr:`~module."

"__package__` and :attr:`~module.__loader__` attributes are filled in (all "

"but :attr:`!__name__` are set to ``None``). The caller is responsible for "

"setting a :attr:`~module.__file__` attribute."

msgstr ""

msgid "Return ``NULL`` with an exception set on error."

msgstr ""

msgid ""

":attr:`~module.__package__` and :attr:`~module.__loader__` are now set to "

"``None``."

msgstr ""

msgid ""

"Similar to :c:func:`PyModule_NewObject`, but the name is a UTF-8 encoded "

"string instead of a Unicode object."

msgstr ""

msgid ""

"Return the dictionary object that implements *module*'s namespace; this "

"object is the same as the :attr:`~object.__dict__` attribute of the module "

"object. If *module* is not a module object (or a subtype of a module "

"object), :exc:`SystemError` is raised and ``NULL`` is returned."

msgstr ""

msgid ""

"It is recommended extensions use other ``PyModule_*`` and ``PyObject_*`` "

"functions rather than directly manipulate a module's :attr:`~object."

"__dict__`."

msgstr ""

msgid ""

"The returned reference is borrowed from the module; it is valid until the "

"module is destroyed."

msgstr ""

msgid ""

"Return *module*'s :attr:`~module.__name__` value. If the module does not "

"provide one, or if it is not a string, :exc:`SystemError` is raised and "

"``NULL`` is returned."

msgstr ""

msgid ""

"Similar to :c:func:`PyModule_GetNameObject` but return the name encoded to "

"``'utf-8'``."

msgstr ""

msgid ""

"The returned buffer is only valid until the module is renamed or destroyed. "

"Note that Python code may rename a module by setting its :py:attr:`~module."

"__name__` attribute."

msgstr ""

msgid ""

"Return a pointer to the :c:type:`PyModuleDef` struct from which the module "

"was created, or ``NULL`` if the module wasn't created from a definition."

msgstr ""

msgid ""

"On error, return ``NULL`` with an exception set. Use :c:func:"

"`PyErr_Occurred` to tell this case apart from a missing :c:type:`!"

"PyModuleDef`."

msgstr ""

msgid ""

"Return the name of the file from which *module* was loaded using *module*'s :"

"attr:`~module.__file__` attribute. If this is not defined, or if it is not "

"a string, raise :exc:`SystemError` and return ``NULL``; otherwise return a "

"reference to a Unicode object."

msgstr ""

msgid ""

"Similar to :c:func:`PyModule_GetFilenameObject` but return the filename "

"encoded to 'utf-8'."

msgstr ""

msgid ""

"The returned buffer is only valid until the module's :py:attr:`~module."

"__file__` attribute is reassigned or the module is destroyed."

msgstr ""

msgid ""

":c:func:`PyModule_GetFilename` raises :exc:`UnicodeEncodeError` on "

"unencodable filenames, use :c:func:`PyModule_GetFilenameObject` instead."

msgstr ""

msgid "Module definition"

msgstr ""

msgid ""

"Modules created using the C API are typically defined using an array of :c:"

"type:`PySlot` structs, which provides a \"description\" of how a module "

"should be created. See :ref:`capi-slots` for more information on slots in "

"general."

msgstr ""

msgid ""

"Previously, a :c:type:`PyModuleDef` struct was necessary to define modules. "

"The older way of defining modules is still available: consult either the :"

"ref:`pymoduledef` section or earlier versions of this documentation if you "

"plan to support earlier Python versions."

msgstr ""

msgid ""

"The slots array is usually used to define an extension module's “main” "

"module object (see :ref:`extension-modules` for details). It can also be "

"used to :ref:`create extension modules dynamically <module-from-slots>`."

msgstr ""

msgid ""

"Unless specified otherwise, the same slot ID may not be repeated in an array "

"of slots."

msgstr ""

msgid "Metadata slots"

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for the name of the new module, as a NUL-"

"terminated UTF8-encoded ``const char *``."

msgstr ""

msgid ""

"Note that modules are typically created using a :py:class:`~importlib."

"machinery.ModuleSpec`, and when they are, the name from the spec will be "

"used instead of :c:data:`!Py_mod_name`. However, it is still recommended to "

"include this slot for introspection and debugging purposes."

msgstr ""

msgid ""

"Use :c:member:`PyModuleDef.m_name` instead to support previous versions."

msgstr ""

msgid ""

":c:type:`Slot ID <PySlot.sl_id>` for the docstring of the new module, as a "

"NUL-terminated UTF8-encoded ``const char *``."

msgstr ""

msgid "Usually it is set to a variable created with :c:macro:`PyDoc_STRVAR`."

msgstr ""

msgid "Use :c:member:`PyModuleDef.m_doc` instead to support previous versions."

msgstr ""

msgid "Feature slots"

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` whose value points to a :c:struct:"

"`PyABIInfo` structure describing the ABI that the extension is using."

msgstr ""

msgid ""

"A suitable :c:struct:`!PyABIInfo` variable can be defined using the :c:macro:"

"`PyABIInfo_VAR` macro, as in:"

msgstr ""

msgid ""

"PyABIInfo_VAR(abi_info);\n"

"\n"

"static PySlot mymodule_slots[] = {\n"

" PySlot_DATA(Py_mod_abi, &abi_info),\n"

" ...\n"

"};"

msgstr ""

msgid ""

"When creating a module, Python checks the value of this slot using :c:func:"

"`PyABIInfo_Check`."

msgstr ""

msgid ""

"This slot is required, except for modules created from :c:struct:"

"`PyModuleDef`."

msgstr ""

msgid ":c:member:`Slot ID <PySlot.sl_id>` whose value is one of:"

msgstr ""

msgid "The module does not support being imported in subinterpreters."

msgstr ""

msgid ""

"The module supports being imported in subinterpreters, but only when they "

"share the main interpreter's GIL. (See :ref:`isolating-extensions-howto`.)"

msgstr ""

msgid ""

"The module supports being imported in subinterpreters, even when they have "

"their own GIL. (See :ref:`isolating-extensions-howto`.)"

msgstr ""

msgid ""

"This slot determines whether or not importing this module in a "

"subinterpreter will fail."

msgstr ""

msgid ""

"If ``Py_mod_multiple_interpreters`` is not specified, the import machinery "

"defaults to ``Py_MOD_MULTIPLE_INTERPRETERS_SUPPORTED``."

msgstr ""

msgid ""

"For historical reasons, the values are declared as pointers (``void *``). "

"When using :c:type:`PySlot` arrays, use :c:macro:`PySlot_DATA` for :c:macro:"

"`!Py_mod_multiple_interpreters`:"

msgstr ""

msgid ""

"PySlot_DATA(Py_mod_multiple_interpreters,\n"

" Py_MOD_PER_INTERPRETER_GIL_SUPPORTED)"

msgstr ""

msgid ""

"The module depends on the presence of the global interpreter lock (GIL), and "

"may access global state without synchronization."

msgstr ""

msgid "The module is safe to run without an active GIL."

msgstr ""

msgid ""

"This slot is ignored by Python builds not configured with :option:`--disable-"

"gil`. Otherwise, it determines whether or not importing this module will "

"cause the GIL to be automatically enabled. See :ref:`whatsnew313-free-"

"threaded-cpython` for more detail."

msgstr ""

msgid ""

"If ``Py_mod_gil`` is not specified, the import machinery defaults to "

"``Py_MOD_GIL_USED``."

msgstr ""

msgid ""

"For historical reasons, the values are declared as pointers (``void *``). "

"When using :c:type:`PySlot` arrays, use :c:macro:`PySlot_DATA` for :c:macro:"

"`!Py_mod_gil`:"

msgstr ""

msgid "PySlot_DATA(Py_mod_gil, Py_MOD_GIL_NOT_USED)"

msgstr ""

msgid "Creation and initialization slots"

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a function that creates the module "

"object itself. The function must have the signature:"

msgstr ""

msgid "The function will be called with:"

msgstr ""

msgid ""

"*spec*: a ``ModuleSpec``-like object, meaning that any attributes defined "

"for :py:class:`importlib.machinery.ModuleSpec` have matching semantics. "

"However, any of the attributes may be missing."

msgstr ""

msgid ""

"*def*: ``NULL``, or the module definition if the module is created from one."

msgstr ""

msgid ""

"The function should return a new module object, or set an error and return "

"``NULL``."

msgstr ""

msgid ""

"This function should be kept minimal. In particular, it should not call "

"arbitrary Python code, as trying to import the same module again may result "

"in an infinite loop."

msgstr ""

msgid ""

"If ``Py_mod_create`` is not specified, the import machinery will create a "

"normal module object using :c:func:`PyModule_New`. The name is taken from "

"*spec*, not the definition, to allow extension modules to dynamically adjust "

"to their place in the module hierarchy and be imported under different names "

"through symlinks, all while sharing a single module definition."

msgstr ""

msgid ""

"There is no requirement for the returned object to be an instance of :c:type:"

"`PyModule_Type`. However, some slots may only be used with :c:type:`!"

"PyModule_Type` instances; in particular:"

msgstr ""

msgid ":c:macro:`Py_mod_exec`,"

msgstr ""

msgid ""

":ref:`module state slots <ext-module-state-slots>` (``Py_mod_state_*``),"

msgstr ""

msgid ":c:macro:`Py_mod_token`."

msgstr ""

msgid ""

"The *slots* argument may be a ``ModuleSpec``-like object, rather than a "

"true :py:class:`~importlib.machinery.ModuleSpec` instance. Note that "

"previous versions of CPython did not enforce this."

msgstr ""

msgid ""

"The *def* argument may now be ``NULL``, since modules are not necessarily "

"made from definitions."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a function that will :dfn:`execute`, "

"or initialize, the module. This function does the equivalent to executing "

"the code of a Python module: typically, it adds classes and constants to the "

"module. The signature of the function is:"

msgstr ""

msgid ""

"See the :ref:`capi-module-support-functions` section for some useful "

"functions to call."

msgstr ""

msgid ""

"For backwards compatibility, the :c:type:`PyModuleDef.m_slots` array may "

"contain multiple :c:macro:`!Py_mod_exec` slots; these are processed in the "

"order they appear in the array. Elsewhere (that is, in arguments to :c:func:"

"`PyModule_FromSlotsAndSpec` and in return values of :samp:"

"`PyModExport_{<name>}`), repeating the slot is not allowed."

msgstr ""

msgid ""

"Repeated ``Py_mod_exec`` slots are disallowed, except in :c:type:"

"`PyModuleDef.m_slots`."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a table of module-level functions, as "

"an array of :c:type:`PyMethodDef` values suitable as the *functions* "

"argument to :c:func:`PyModule_AddFunctions`."

msgstr ""

msgid ""

"Like other slot IDs, a slots array may only contain one :c:macro:`!"

"Py_mod_methods` entry. To add functions from multiple :c:type:`PyMethodDef` "

"arrays, call :c:func:`PyModule_AddFunctions` in the :c:macro:`Py_mod_exec` "

"function."

msgstr ""

msgid ""

"The table must be statically allocated (or otherwise guaranteed to outlive "

"the module object)."

msgstr ""

msgid ""

"Use :c:member:`PyModuleDef.m_methods` instead to support previous versions."

msgstr ""

msgid "Module state"

msgstr ""

msgid ""

"Extension modules can have *module state* -- a piece of memory that is "

"allocated on module creation, and freed when the module object is "

"deallocated. The module state is specified using :ref:`dedicated slots <ext-"

"module-state-slots>`."

msgstr ""

msgid ""

"A typical use of module state is storing an exception type -- or indeed "

"*any* type object defined by the module --"

msgstr ""

msgid ""

"Unlike the module's Python attributes, Python code cannot replace or delete "

"data stored in module state."

msgstr ""

msgid ""

"Keeping per-module information in attributes and module state, rather than "

"in static globals, makes module objects *isolated* and safer for use in "

"multiple sub-interpreters. It also helps Python do an orderly clean-up when "

"it shuts down."

msgstr ""

msgid ""

"Extensions that keep references to Python objects as part of module state "

"must implement :c:macro:`Py_mod_state_traverse` and :c:macro:"

"`Py_mod_state_clear` functions to avoid reference leaks."

msgstr ""

msgid "To retrieve the state from a given module, use the following functions:"

msgstr ""

msgid ""

"Return the \"state\" of the module, that is, a pointer to the block of "

"memory allocated at module creation time, or ``NULL``. See :c:macro:"

"`Py_mod_state_size`."

msgstr ""

msgid ""

"On error, return ``NULL`` with an exception set. Use :c:func:"

"`PyErr_Occurred` to tell this case apart from missing module state."

msgstr ""

msgid ""

"Set *\\*result* to the size of *module*'s state, as specified using :c:macro:"

"`Py_mod_state_size` (or :c:member:`PyModuleDef.m_size`), and return 0."

msgstr ""

msgid "On error, set *\\*result* to -1, and return -1 with an exception set."

msgstr ""

msgid "Slots for defining module state"

msgstr ""

msgid ""

"The following :c:member:`slot IDs <PySlot.sl_id>` are available for "

"defining the module state."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for the size of the module state, in "

"bytes."

msgstr ""

msgid ""

"Setting the value to a non-negative value means that the module can be re-"

"initialized and specifies the additional amount of memory it requires for "

"its state."

msgstr ""

msgid "See :PEP:`3121` for more details."

msgstr ""

msgid ""

"Use :c:func:`PyModule_GetStateSize` to retrieve the size of a given module."

msgstr ""

msgid ""

"Use :c:member:`PyModuleDef.m_size` instead to support previous versions."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a traversal function to call during "

"GC traversal of the module object."

msgstr ""

msgid ""

"The signature of the function, and meanings of the arguments, is similar as "

"for :c:member:`PyTypeObject.tp_traverse`:"

msgstr ""

msgid ""

"This function is not called if the module state was requested but is not "

"allocated yet. This is the case immediately after the module is created and "

"before the module is executed (:c:data:`Py_mod_exec` function). More "

"precisely, this function is not called if the state size (:c:data:"

"`Py_mod_state_size`) is greater than 0 and the module state (as returned by :"

"c:func:`PyModule_GetState`) is ``NULL``."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a clear function to call during GC "

"clearing of the module object."

msgstr ""

msgid "The signature of the function is:"

msgstr ""

msgid ""

"Like :c:member:`PyTypeObject.tp_clear`, this function is not *always* called "

"before a module is deallocated. For example, when reference counting is "

"enough to determine that an object is no longer used, the cyclic garbage "

"collector is not involved and the :c:macro:`Py_mod_state_free` function is "

"called directly."

msgstr ""

msgid ""

"Use :c:member:`PyModuleDef.m_clear` instead to support previous versions."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` for a function to call during "

"deallocation of the module object."

msgstr ""

msgid ""

"Use :c:member:`PyModuleDef.m_free` instead to support previous versions."

msgstr ""

msgid "Module token"

msgstr ""

msgid ""

"Each module may have an associated *token*: a pointer-sized value intended "

"to identify of the module state's memory layout. This means that if you have "

"a module object, but you are not sure if it “belongs” to your extension, you "

"can check using code like this:"

msgstr ""

msgid ""

"PyObject *module = <the module in question>\n"

"\n"

"void *module_token;\n"

"if (PyModule_GetToken(module, &module_token) < 0) {\n"

" return NULL;\n"

"}\n"

"if (module_token != your_token) {\n"

" PyErr_SetString(PyExc_ValueError, \"unexpected module\")\n"

" return NULL;\n"

"}\n"

"\n"

"// This module's state has the expected memory layout; it's safe to cast\n"

"struct my_state state = (struct my_state*)PyModule_GetState(module)"

msgstr ""

msgid ""

"A module's token -- and the *your_token* value to use in the above code -- "

"is:"

msgstr ""

msgid ""

"For modules created with :c:type:`PyModuleDef`: the address of that :c:type:"

"`PyModuleDef`;"

msgstr ""

msgid ""

"For modules defined with the :c:macro:`Py_mod_token` slot: the value of that "

"slot;"

msgstr ""

msgid ""

"For modules created from an ``PyModExport_*`` :ref:`export hook <extension-"

"export-hook>`: the slots array that the export hook returned (unless "

"overridden with :c:macro:`Py_mod_token`)."

msgstr ""

msgid ":c:member:`Slot ID <PySlot.sl_id>` for the module token."

msgstr ""

msgid ""

"If you use this slot to set the module token (rather than rely on the "

"default), you must ensure that:"

msgstr ""

msgid ""

"The pointer outlives the class, so it's not reused for something else while "

"the class exists."

msgstr ""

msgid ""

"It \"belongs\" to the extension module where the class lives, so it will not "

"clash with other extensions."

msgstr ""

msgid ""

"If the token points to a :c:type:`PyModuleDef` struct, the module should "

"behave as if it was created from that :c:type:`PyModuleDef`. In particular, "

"the module state must have matching layout and semantics."

msgstr ""

msgid ""

"Modules created from :c:type:`PyModuleDef` always use the address of the :c:"

"type:`PyModuleDef` as the token. This means that :c:macro:`!Py_mod_token` "

"cannot be used in :c:member:`PyModuleDef.m_slots`."

msgstr ""

msgid "Set *\\*result* to the module token for *module* and return 0."

msgstr ""

msgid "On error, set *\\*result* to NULL, and return -1 with an exception set."

msgstr ""

msgid "See also :c:func:`PyType_GetModuleByToken`."

msgstr ""

msgid "Creating extension modules dynamically"

msgstr ""

msgid ""

"The following functions may be used to create an extension module "

"dynamically, rather than from an extension's :ref:`export hook <extension-"

"export-hook>`."

msgstr ""

msgid ""

"Create a new module object, given an array of :ref:`slots "

"<pymoduledef_slot>` and the :py:class:`~importlib.machinery.ModuleSpec` "

"*spec*."

msgstr ""

msgid ""

"The *slots* argument must point to an array of :c:type:`PySlot` structures, "

"terminated by an entry with slot ID of 0 (typically written as :c:macro:"

"`PySlot_END`). The array must include a :c:data:`Py_mod_abi` entry."

msgstr ""

msgid ""

"The *spec* argument may be any ``ModuleSpec``-like object, as described in :"

"c:macro:`Py_mod_create` documentation. Currently, the *spec* must have a "

"``name`` attribute."

msgstr ""

msgid ""

"On success, return the new module. On error, return ``NULL`` with an "

"exception set."

msgstr ""

msgid ""

"Note that this does not process the module's execution slot (:c:data:"

"`Py_mod_exec`). Both :c:func:`!PyModule_FromSlotsAndSpec` and :c:func:"

"`PyModule_Exec` must be called to fully initialize a module. (See also :ref:"

"`multi-phase-initialization`.)"

msgstr ""

msgid "Execute the :c:data:`Py_mod_exec` slot(s) of *module*."

msgstr ""

msgid "On success, return 0. On error, return -1 with an exception set."

msgstr ""

msgid ""

"For clarity: If *module* has no slots, for example if it uses :ref:`legacy "

"single-phase initialization <single-phase-initialization>`, this function "

"does nothing and returns 0."

msgstr ""

msgid "Module definition struct"

msgstr ""

msgid ""

"Traditionally, extension modules were defined using a *module definition* as "

"the “description\" of how a module should be created. Rather than using an "

"array of :ref:`slots <pymoduledef_slot>` directly, the definition has "

"dedicated members for most common functionality, and allows additional slots "

"as an extension mechanism."

msgstr ""

msgid ""

"This way of defining modules is still available and there are no plans to "

"remove it."

msgstr ""

msgid ""

"The module definition struct, which holds information needed to create a "

"module object."

msgstr ""

msgid ""

"This structure must be statically allocated (or be otherwise guaranteed to "

"be valid while any modules created from it exist). Usually, there is only "

"one variable of this type for each extension module defined this way."

msgstr ""

msgid ""

"The struct, including all members, is part of the :ref:`Stable ABI <stable-"

"abi>` for non-free-threaded builds (``abi3``). In the Stable ABI for free-"

"threaded builds (``abi3t``), this struct is opaque, and unusable in "

"practice; see :ref:`pymoduledef_slot` for a replacement."

msgstr ""

msgid "Always initialize this member to :c:macro:`PyModuleDef_HEAD_INIT`:"

msgstr ""

msgid "The type of :c:member:`!PyModuleDef.m_base`."

msgstr ""

msgid ""

"The struct is part of the :ref:`Stable ABI <stable-abi>` for non-free-"

"threaded builds (``abi3``). In the Stable ABI for Free-Threaded Builds "

"(``abi3t``), this struct is opaque, and unusable in practice."

msgstr ""

msgid "The required initial value for :c:member:`!PyModuleDef.m_base`."

msgstr ""

msgid "Corresponds to the :c:macro:`Py_mod_name` slot."

msgstr ""

msgid ""

"These members correspond to the :c:macro:`Py_mod_doc` slot. Setting this to "

"NULL is equivalent to omitting the slot."

msgstr ""

msgid ""

"Corresponds to the :c:macro:`Py_mod_state_size` slot. Setting this to zero "

"is equivalent to omitting the slot."

msgstr ""

msgid ""

"When using :ref:`legacy single-phase initialization <single-phase-"

"initialization>` or when creating modules dynamically using :c:func:"

"`PyModule_Create` or :c:func:`PyModule_Create2`, :c:member:`!m_size` may be "

"set to -1. This indicates that the module does not support sub-interpreters, "

"because it has global state."

msgstr ""

msgid ""

"Corresponds to the :c:macro:`Py_mod_methods` slot. Setting this to NULL is "

"equivalent to omitting the slot."

msgstr ""

msgid ""

"An array of additional slots, terminated by a ``{0, NULL}`` entry. Note that "

"the entries use the older :c:type:`PyModuleDef_Slot` structure, rather than :"

"c:type:`PySlot`."

msgstr ""

msgid ""

"If the array contains slots corresponding to :c:type:`PyModuleDef` members, "

"the values must match. For example, if you use :c:macro:`Py_mod_name` in :c:"

"member:`!m_slots`, :c:member:`PyModuleDef.m_name` must be set to the same "

"pointer (not just an equal string)."

msgstr ""

msgid ""

"Prior to version 3.5, this member was always set to ``NULL``, and was "

"defined as:"

msgstr ""

msgid "Older structure defining additional slots of a module."

msgstr ""

msgid ""

"Note that a :c:type:`!PyModuleDef_Slot` array may be included in a :c:type:`!"

"PySlot` array using :c:macro:`Py_mod_slots`, and vice versa using :c:macro:"

"`Py_slot_subslots`."

msgstr ""

msgid ""

"Each :c:type:`!PyModuleDef_Slot` structure ``modslot`` is interpreted as the "

"following :c:type:`PySlot` structure::"

msgstr ""

msgid ""

"(PySlot){\n"

" .sl_id=modslot.slot,\n"

" .sl_flags=PySlot_INTPTR | sub_static,\n"

" .sl_ptr=modslot.value\n"

"}"

msgstr ""

msgid ""

"where ``sub_static`` is ``PySlot_STATIC`` if the slot requires the flag "

"(such as for :c:macro:`Py_mod_methods`), or if this flag is present on the "

"\"parent\" :c:macro:`!Py_mod_slots` slot (if any)."

msgstr ""

msgid "Corresponds to :c:member:`PySlot.sl_id`."

msgstr ""

msgid "Corresponds to :c:member:`PySlot.sl_ptr`."

msgstr ""

msgid ""

"These members correspond to the :c:macro:`Py_mod_state_traverse`, :c:macro:"

"`Py_mod_state_clear`, and :c:macro:`Py_mod_state_free` slots, respectively."

msgstr ""

msgid ""

"Setting these members to NULL is equivalent to omitting the corresponding "

"slots."

msgstr ""

msgid ""

":c:member:`m_traverse`, :c:member:`m_clear` and :c:member:`m_free` functions "

"are no longer called before the module state is allocated."

msgstr ""

msgid "The type of ``PyModuleDef`` objects."

msgstr ""

msgid ""

":c:member:`Slot ID <PySlot.sl_id>` that works like :c:macro:"

"`Py_slot_subslots`, except it specifies an array of :c:type:"

"`PyModuleDef_Slot` structures."

msgstr ""

msgid ""

"The following API can be used to create modules from a :c:type:`!"

"PyModuleDef` struct:"

msgstr ""

msgid ""

"Create a new module object, given the definition in *def*. This is a macro "

"that calls :c:func:`PyModule_Create2` with *module_api_version* set to :c:"

"macro:`PYTHON_API_VERSION`, or to :c:macro:`PYTHON_ABI_VERSION` if using "

"the :ref:`limited API <limited-c-api>`."

msgstr ""

msgid ""

"Create a new module object, given the definition in *def*, assuming the API "

"version *module_api_version*. If that version does not match the version of "

"the running interpreter, a :exc:`RuntimeWarning` is emitted."

msgstr ""

msgid ""

"This function does not support slots. The :c:member:`~PyModuleDef.m_slots` "

"member of *def* must be ``NULL``."

msgstr ""

msgid ""

"Most uses of this function should be using :c:func:`PyModule_Create` "

"instead; only use this if you are sure you need it."

msgstr ""

msgid ""

"This macro calls :c:func:`PyModule_FromDefAndSpec2` with "

"*module_api_version* set to :c:macro:`PYTHON_API_VERSION`, or to :c:macro:"

"`PYTHON_ABI_VERSION` if using the :ref:`limited API <limited-c-api>`."

msgstr ""

msgid "Prefer :c:func:`PyModule_FromSlotsAndSpec` in new code."

msgstr ""

msgid ""

"Create a new module object, given the definition in *def* and the ModuleSpec "

"*spec*, assuming the API version *module_api_version*. If that version does "

"not match the version of the running interpreter, a :exc:`RuntimeWarning` is "

"emitted."

msgstr ""

msgid ""

"Note that this does not process execution slots (:c:data:`Py_mod_exec`). "

"Both ``PyModule_FromDefAndSpec`` and ``PyModule_ExecDef`` must be called to "

"fully initialize a module."

msgstr ""

msgid ""

"Most uses of this function should be using :c:func:`PyModule_FromDefAndSpec` "

"instead; only use this if you are sure you need it."

msgstr ""

msgid "Process any execution slots (:c:data:`Py_mod_exec`) given in *def*."

msgstr ""

msgid ""

"To run a module's own execution slots, prefer :c:func:`PyModule_Exec`, which "

"works on modules that were not created from a :c:type:`PyModuleDef` "

"structure."

msgstr ""

msgid ""

"The C API version, as an integer (``1013``) and string (``\"1013\"``), "

"respectively. Defined for backwards compatibility."

msgstr ""

msgid ""

"Currently, this constant is not updated in new Python versions, and is not "

"useful for versioning. This may change in the future."

msgstr ""

msgid ""

"Defined as ``3`` and ``\"3\"``, respectively, for backwards compatibility."

msgstr ""

msgid "Support functions"

msgstr ""

msgid ""

"The following functions are provided to help initialize a module object. "

"They are intended for a module's execution slot (:c:data:`Py_mod_exec`), the "

"initialization function for legacy :ref:`single-phase initialization <single-"

"phase-initialization>`, or code that creates modules dynamically."

msgstr ""

msgid ""

"Add an object to *module* as *name*. This is a convenience function which "

"can be used from the module's initialization function."

msgstr ""

msgid ""

"On success, return ``0``. On error, raise an exception and return ``-1``."

msgstr ""

msgid "Example usage::"

msgstr ""

msgid ""

"static int\n"

"add_spam(PyObject *module, int value)\n"

"{\n"

" PyObject *obj = PyLong_FromLong(value);\n"

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

" return -1;\n"

" }\n"

" int res = PyModule_AddObjectRef(module, \"spam\", obj);\n"

" Py_DECREF(obj);\n"

" return res;\n"

" }"

msgstr ""

msgid ""

"To be convenient, the function accepts ``NULL`` *value* with an exception "

"set. In this case, return ``-1`` and just leave the raised exception "

"unchanged."

msgstr ""

msgid ""

"The example can also be written without checking explicitly if *obj* is "

"``NULL``::"

msgstr ""

msgid ""

"static int\n"

"add_spam(PyObject *module, int value)\n"

"{\n"

" PyObject *obj = PyLong_FromLong(value);\n"

" int res = PyModule_AddObjectRef(module, \"spam\", obj);\n"

" Py_XDECREF(obj);\n"

" return res;\n"

" }"

msgstr ""

msgid ""

"Note that ``Py_XDECREF()`` should be used instead of ``Py_DECREF()`` in this "

"case, since *obj* can be ``NULL``."

msgstr ""

msgid ""

"The number of different *name* strings passed to this function should be "

"kept small, usually by only using statically allocated strings as *name*. "

"For names that aren't known at compile time, prefer calling :c:func:"

"`PyUnicode_FromString` and :c:func:`PyObject_SetAttr` directly. For more "

"details, see :c:func:`PyUnicode_InternFromString`, which may be used "

"internally to create a key object."

msgstr ""

msgid ""

"Similar to :c:func:`PyModule_AddObjectRef`, but \"steals\" a reference to "

"*value*. It can be called with a result of function that returns a new "

"reference without bothering to check its result or even saving it to a "

"variable."

msgstr ""

msgid ""

"if (PyModule_Add(module, \"spam\", PyBytes_FromString(value)) < 0) {\n"

" goto error;\n"

"}"

msgstr ""

msgid ""

"Similar to :c:func:`PyModule_AddObjectRef`, but steals a reference to "

"*value* on success (if it returns ``0``)."

msgstr ""

msgid ""

"The new :c:func:`PyModule_Add` or :c:func:`PyModule_AddObjectRef` functions "

"are recommended, since it is easy to introduce reference leaks by misusing "

"the :c:func:`PyModule_AddObject` function."

msgstr ""

msgid ""

"Unlike other functions that steal references, ``PyModule_AddObject()`` only "

"releases the reference to *value* **on success**."

msgstr ""