Hi, In 2017, I proposed to document the feature, but nobody was volunteer to write the doc (issue still open): https://bugs.python.org/issue25571
I added a bare minimum mention of this feature in the "Python Debug Build" documentation: https://docs.python.org/dev/using/configure.html#python-debug-build A bug was fixed in 2018, so it has at least one user :-) https://bugs.python.org/issue34113 In 2017, adding an API to trace instructions with sys.settrace() was discussed, but the idea got rejected: * https://bugs.python.org/issue29400 * https://mail.python.org/pipermail/python-dev/2017-September/149632.html IMO it would be more flexible than the current "lltrace" implementation which hardcode writing bytecode into C stdout stream which is not convenient and cannot be easily redirected. I have no idea if it would be possible to provide an *efficient* implementation of such hook in ceval.c, even if it's only implemented in debug build. Victor _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/M6R6EWL2FS5SZC4A3ZDIPZH2LI6G4TFO/ Code of Conduct: http://python.org/psf/codeofconduct/
