-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
sys.settrace
does not receive opcode
events in 3.12.x
#114480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Verified on Windows. |
dup #103615 which is fixed in main by #109472 This is an issue introduced by PEP 669 and it's a design issue. The workaround is to set any |
If fix is not backportable then I would prefer this bug and the workaround to be documented somewhere, preferrably in the |
I'm not against documenting this for 3.12 only. We need to consult docs team about how to do this properly. |
This comment was marked as spam.
This comment was marked as spam.
This behavior is documented in 3.12, so close this issue. |
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
When running in versions
3.11.7
and3.13.0a3
, opcode events are emitted, though they differ:podman run --rm -it -v (pwd)/tracetest.py:/tracetest.py:Z python:3.11.7 python /tracetest.py
podman run --rm -it -v (pwd)/tracetest.py:/tracetest.py:Z python:3.13.0a3 python /tracetest.py
However on 3.12.0 and 3.12.1, only
call
,line
andreturn
are emitted:podman run --rm -it -v (pwd)/tracetest.py:/tracetest.py:Z python:3.12.1 python /tracetest.py
CPython versions tested on:
3.12
Operating systems tested on:
Linux
Linked PRs
The text was updated successfully, but these errors were encountered: