iframe-proxy | Sunbelt Computer Software

250 lines (195 loc) · 7.22 KB
# 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
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-06-21 15:47+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Monitoring C API"
msgid "Added in version 3.13."
"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`."
msgid "Generating Execution Events"
"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."
"The VM disables tracing when firing an event, so there is no need for user "
"code to do that."
"Monitoring functions should not be called with an exception set, except "
"those listed below as working with the current exception."
"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 "
"All of the functions below return 0 on success and -1 (with an exception "
"set) on error."
msgid "See :mod:`sys.monitoring` for descriptions of the events."
msgid "Fire a ``PY_START`` event."
msgid "Fire a ``PY_RESUME`` event."
msgid "Fire a ``PY_RETURN`` event."
msgid "Fire a ``PY_YIELD`` event."
msgid "Fire a ``CALL`` event."
msgid "Fire a ``LINE`` event."
msgid "Fire a ``JUMP`` event."
msgid "Fire a ``BRANCH_LEFT`` event."
msgid "Fire a ``BRANCH_RIGHT`` event."
msgid "Fire a ``C_RETURN`` event."
"Fire a ``PY_THROW`` event with the current exception (as returned by :c:func:"
"`PyErr_GetRaisedException`)."
"Fire a ``RAISE`` event with the current exception (as returned by :c:func:"
"`PyErr_GetRaisedException`)."
"Fire a ``C_RAISE`` event with the current exception (as returned by :c:func:"
"`PyErr_GetRaisedException`)."
"Fire a ``RERAISE`` event with the current exception (as returned by :c:func:"
"`PyErr_GetRaisedException`)."
"Fire an ``EXCEPTION_HANDLED`` event with the current exception (as returned "
"by :c:func:`PyErr_GetRaisedException`)."
"Fire a ``PY_UNWIND`` event with the current exception (as returned by :c:"
"func:`PyErr_GetRaisedException`)."
"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."
msgid "Managing the Monitoring State"
"Monitoring states can be managed with the help of monitoring scopes. A scope "
"would typically correspond to a Python function."
"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``."
"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."
"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."
msgid "The macros for *event_types* are:"
msgid "Macro"
msgid "Event"
msgstr "Zdarzenie"
msgid ":monitoring-event:`BRANCH_LEFT`"
msgstr ":monitoring-event:`BRANCH_LEFT`"
msgid ":monitoring-event:`BRANCH_RIGHT`"
msgstr ":monitoring-event:`BRANCH_RIGHT`"
msgid ":monitoring-event:`CALL`"
msgstr ":monitoring-event:`CALL`"
msgid ":monitoring-event:`C_RAISE`"
msgstr ":monitoring-event:`C_RAISE`"
msgid ":monitoring-event:`C_RETURN`"
msgstr ":monitoring-event:`C_RETURN`"
msgid ":monitoring-event:`EXCEPTION_HANDLED`"
msgstr ":monitoring-event:`EXCEPTION_HANDLED`"
msgid ":monitoring-event:`INSTRUCTION`"
msgstr ":monitoring-event:`INSTRUCTION`"
msgid ":monitoring-event:`JUMP`"
msgstr ":monitoring-event:`JUMP`"
msgid ":monitoring-event:`LINE`"
msgstr ":monitoring-event:`LINE`"
msgid ":monitoring-event:`PY_RESUME`"
msgstr ":monitoring-event:`PY_RESUME`"
msgid ":monitoring-event:`PY_RETURN`"
msgstr ":monitoring-event:`PY_RETURN`"
msgid ":monitoring-event:`PY_START`"
msgstr ":monitoring-event:`PY_START`"
msgid ":monitoring-event:`PY_THROW`"
msgstr ":monitoring-event:`PY_THROW`"
msgid ":monitoring-event:`PY_UNWIND`"
msgstr ":monitoring-event:`PY_UNWIND`"
msgid ":monitoring-event:`PY_YIELD`"
msgstr ":monitoring-event:`PY_YIELD`"
msgid ":monitoring-event:`RAISE`"
msgstr ":monitoring-event:`RAISE`"
msgid ":monitoring-event:`RERAISE`"
msgstr ":monitoring-event:`RERAISE`"
msgid ":monitoring-event:`STOP_ITERATION`"
msgstr ":monitoring-event:`STOP_ITERATION`"
"Exit the last scope that was entered with :c:func:`!PyMonitoring_EnterScope`."
"Return true if the event corresponding to the event ID *ev* is a :ref:`local "
"event <monitoring-event-local>`."
Sunbelt Computer Software

PL/B Language Development and Support

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Sunbelt Computer Software

PL/B Language Development and Support

Uh oh!

Uh oh!

FilesExpand file tree

monitoring.po

Latest commit

History

monitoring.po

File metadata and controls
