PEP 669: Clarify and restrict interaction with PEP 523 (#2760)
This commit is contained in:
parent
9819ca468e
commit
39b78da33b
13
pep-0669.rst
13
pep-0669.rst
|
@ -288,13 +288,16 @@ Backwards Compatibility
|
||||||
This PEP is mostly backwards compatible.
|
This PEP is mostly backwards compatible.
|
||||||
|
|
||||||
This PEP is incompatible with :pep:`523` as the behavior would be undefined,
|
This PEP is incompatible with :pep:`523` as the behavior would be undefined,
|
||||||
as we have no control over the behavior of :pep:`523` plugins.
|
since the VM has no control over the behavior of :pep:`523` plugins.
|
||||||
|
|
||||||
Thus, if :pep:`523` is in use, then calling ``sys.monitoring.set_events()`` or
|
Thus, if ``_PyInterpreterState_SetEvalFrameFunc()`` has been called and has
|
||||||
``sys.monitoring.set_local_events()`` will raise an exception.
|
changed the frame evaluation function, then calling
|
||||||
|
``sys.monitoring.set_events()``, ``sys.monitoring.set_local_events()``, or
|
||||||
|
``sys.monitoring.insert_marker`` will raise an exception.
|
||||||
|
|
||||||
Likewise, if ``sys.monitoring.set_events()`` or
|
Likewise, if ``sys.monitoring.set_events()``,
|
||||||
``sys.monitoring.set_local_events()`` has been called, then using :pep:`523`
|
``sys.monitoring.set_local_events()``, or ``sys.monitoring.insert_marker``
|
||||||
|
has been called, then calling ``_PyInterpreterState_SetEvalFrameFunc()``
|
||||||
will raise an exception.
|
will raise an exception.
|
||||||
|
|
||||||
``sys.settrace`` and ``sys.setprofile`` will act as if they were tools 6 and 7
|
``sys.settrace`` and ``sys.setprofile`` will act as if they were tools 6 and 7
|
||||||
|
|
Loading…
Reference in New Issue