Implement and document PEP 669. #103082
Description
Now that PEP 669 is accepted, it needs to be implemented and documented.
- Implement the PEP
- Decide on and implement policy for monitors seeing the code in other monitors.
- Document the PEP
- Use "macro" instructions to reduce code duplication in bytecodes.c
Linked PRs
- GH-103082: Implementation of PEP 669: Low Impact Monitoring for CPython #103083
- GH-103082: Code cleanup from review. #103474
- GH-103082: Turn on branch events for FOR_ITER instructions. #103507
- gh-103082: Fix shifted field initialization in
instrumentation.c#103561 - GH-103082: Filter LINE events in VM, to simplify tool implementation. #104387
- GH-103082: Rename PY_MONITORING_EVENTS to _PY_MONITORING_EVENTS #107069
- [3.12] GH-103082: Rename PY_MONITORING_EVENTS to _PY_MONITORING_EVENTS (#107069) #107075
- GH-103082: Document PEP-669: Low Impact Monitoring for CPython #107772
- gh-103082: use IS_VALID_OPCODE instead of _PyOpcode_OpName to check if an opcode is defined #107882
- gh-103082: remove assumption that INSTRUMENTED_LINE is the last instrumented opcode #107978
- [3.12] GH-103082: Document PEP-669: Low Impact Monitoring for CPython (GH-107772) #108909
- [3.12] GH-103082: Clean up the sys.monitoring docs #111048