python-docs-fa/c-api/monitoring.po at fix-machine-translation · python/python-docs-fa

225 lines (173 loc) · 7.42 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2025, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
"Project-Id-Version: Python 3.13\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-10 02:51+0330\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: c-api/monitoring.rst:6
msgid "Monitoring C API"
#: c-api/monitoring.rst:8
msgid "Added in version 3.13."
#: c-api/monitoring.rst:10
msgid "An extension may need to interact with the event monitoring system. Subscribing to events and registering callbacks can be done via the Python API exposed in :mod:`sys.monitoring`."
#: c-api/monitoring.rst:15
msgid "Generating Execution Events"
#: c-api/monitoring.rst:17
msgid "The functions below make it possible for an extension to fire monitoring events as it emulates the execution of Python code. Each of these functions accepts a ``PyMonitoringState`` struct which contains concise information about the activation state of events, as well as the event arguments, which include a ``PyObject*`` representing the code object, the instruction offset and sometimes additional, event-specific arguments (see :mod:`sys.monitoring` for details about the signatures of the different event callbacks). The ``codelike`` argument should be an instance of :class:`types.CodeType` or of a type that emulates it."
#: c-api/monitoring.rst:27
msgid "The VM disables tracing when firing an event, so there is no need for user code to do that."
#: c-api/monitoring.rst:30
msgid "Monitoring functions should not be called with an exception set, except those listed below as working with the current exception."
#: c-api/monitoring.rst:35
msgid "Representation of the state of an event type. It is allocated by the user while its contents are maintained by the monitoring API functions described below."
#: c-api/monitoring.rst:39
msgid "All of the functions below return 0 on success and -1 (with an exception set) on error."
#: c-api/monitoring.rst:41
msgid "See :mod:`sys.monitoring` for descriptions of the events."
#: c-api/monitoring.rst:45
msgid "Fire a ``PY_START`` event."
#: c-api/monitoring.rst:50
msgid "Fire a ``PY_RESUME`` event."
#: c-api/monitoring.rst:55
msgid "Fire a ``PY_RETURN`` event."
#: c-api/monitoring.rst:60
msgid "Fire a ``PY_YIELD`` event."
#: c-api/monitoring.rst:65
msgid "Fire a ``CALL`` event."
#: c-api/monitoring.rst:70
msgid "Fire a ``LINE`` event."
#: c-api/monitoring.rst:75
msgid "Fire a ``JUMP`` event."
#: c-api/monitoring.rst:80
msgid "Fire a ``BRANCH`` event."
#: c-api/monitoring.rst:85
msgid "Fire a ``C_RETURN`` event."
#: c-api/monitoring.rst:90
msgid "Fire a ``PY_THROW`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:96
msgid "Fire a ``RAISE`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:102
msgid "Fire a ``C_RAISE`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:108
msgid "Fire a ``RERAISE`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:114
msgid "Fire an ``EXCEPTION_HANDLED`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:120
msgid "Fire a ``PY_UNWIND`` event with the current exception (as returned by :c:func:`PyErr_GetRaisedException`)."
#: c-api/monitoring.rst:126
msgid "Fire a ``STOP_ITERATION`` event. If ``value`` is an instance of :exc:`StopIteration`, it is used. Otherwise, a new :exc:`StopIteration` instance is created with ``value`` as its argument."
#: c-api/monitoring.rst:131
msgid "Managing the Monitoring State"
#: c-api/monitoring.rst:133
msgid "Monitoring states can be managed with the help of monitoring scopes. A scope would typically correspond to a python function."
#: c-api/monitoring.rst:138
msgid "Enter a monitored scope. ``event_types`` is an array of the event IDs for events that may be fired from the scope. For example, the ID of a ``PY_START`` event is the value ``PY_MONITORING_EVENT_PY_START``, which is numerically equal to the base-2 logarithm of ``sys.monitoring.events.PY_START``. ``state_array`` is an array with a monitoring state entry for each event in ``event_types``, it is allocated by the user but populated by :c:func:`!PyMonitoring_EnterScope` with information about the activation state of the event. The size of ``event_types`` (and hence also of ``state_array``) is given in ``length``."
#: c-api/monitoring.rst:148
msgid "The ``version`` argument is a pointer to a value which should be allocated by the user together with ``state_array`` and initialized to 0, and then set only by :c:func:`!PyMonitoring_EnterScope` itself. It allows this function to determine whether event states have changed since the previous call, and to return quickly if they have not."
#: c-api/monitoring.rst:154
msgid "The scopes referred to here are lexical scopes: a function, class or method. :c:func:`!PyMonitoring_EnterScope` should be called whenever the lexical scope is entered. Scopes can be reentered, reusing the same *state_array* and *version*, in situations like when emulating a recursive Python function. When a code-like's execution is paused, such as when emulating a generator, the scope needs to be exited and re-entered."
#: c-api/monitoring.rst:161
msgid "The macros for *event_types* are:"
#: c-api/monitoring.rst:169
msgid "Macro"
#: c-api/monitoring.rst:169
msgid "Event"
#: c-api/monitoring.rst:171
msgid ":monitoring-event:`BRANCH`"
#: c-api/monitoring.rst:172
msgid ":monitoring-event:`CALL`"
#: c-api/monitoring.rst:173
msgid ":monitoring-event:`C_RAISE`"
#: c-api/monitoring.rst:174
msgid ":monitoring-event:`C_RETURN`"
#: c-api/monitoring.rst:175
msgid ":monitoring-event:`EXCEPTION_HANDLED`"
#: c-api/monitoring.rst:176
msgid ":monitoring-event:`INSTRUCTION`"
#: c-api/monitoring.rst:177
msgid ":monitoring-event:`JUMP`"
#: c-api/monitoring.rst:178
msgid ":monitoring-event:`LINE`"
#: c-api/monitoring.rst:179
msgid ":monitoring-event:`PY_RESUME`"
#: c-api/monitoring.rst:180
msgid ":monitoring-event:`PY_RETURN`"
#: c-api/monitoring.rst:181
msgid ":monitoring-event:`PY_START`"
#: c-api/monitoring.rst:182
msgid ":monitoring-event:`PY_THROW`"
#: c-api/monitoring.rst:183
msgid ":monitoring-event:`PY_UNWIND`"
#: c-api/monitoring.rst:184
msgid ":monitoring-event:`PY_YIELD`"
#: c-api/monitoring.rst:185
msgid ":monitoring-event:`RAISE`"
#: c-api/monitoring.rst:186
msgid ":monitoring-event:`RERAISE`"
#: c-api/monitoring.rst:187
msgid ":monitoring-event:`STOP_ITERATION`"
#: c-api/monitoring.rst:192
msgid "Exit the last scope that was entered with :c:func:`!PyMonitoring_EnterScope`."
Navigation Menu

Uh oh!

Uh oh!

FilesExpand file tree

monitoring.po

Latest commit

History

monitoring.po

File metadata and controls
