iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 669: Update to reflect latest additions. (#3100) 

Update PEP 669 to reflect latest additions.
This commit is contained in:
Mark Shannon 2023-04-11 16:40:41 +01:00 committed by GitHub
parent 086d2a89b7
commit b07d65789d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pep-0669.rst
View File

@ -206,6 +206,7 @@ Events can be controlled globally by modifying the set of events being monitored
* ``sys.monitoring.set_events(tool_id:int, event_set: int)`` * ``sys.monitoring.set_events(tool_id:int, event_set: int)``
Activates all events which are set in ``event_set``. Activates all events which are set in ``event_set``.
Raises a ``ValueError`` if ``tool_id`` is not in use.
No events are active by default. No events are active by default.
@ -219,6 +220,7 @@ Events can also be controlled on a per code object basis:
* ``sys.monitoring.set_local_events(tool_id:int, code: CodeType, event_set: int)`` * ``sys.monitoring.set_local_events(tool_id:int, code: CodeType, event_set: int)``
Activates all the local events for ``code`` which are set in ``event_set``. Activates all the local events for ``code`` which are set in ``event_set``.
Raises a ``ValueError`` if ``tool_id`` is not in use.
Local events add to global events, but do not mask them. Local events add to global events, but do not mask them.
In other words, all global events will trigger for a code object, In other words, all global events will trigger for a code object,
@ -307,8 +309,8 @@ Order of events
If an instructions triggers several events they occur in the following order: If an instructions triggers several events they occur in the following order:
* INSTRUCTION
* LINE * LINE
* INSTRUCTION
* All other events (only one of these events can occur per instruction) * All other events (only one of these events can occur per instruction)
Each event is delivered to tools in ascending order of ID. Each event is delivered to tools in ascending order of ID.