83 ms·
In Python, some of the stated use cases, like extracting coverage, extracting the call graph, etc, you can get via tracing already (sys.settrace, https://docs.p
by albertzeyer 2y ago
In Python, some of the stated use cases, like extracting coverage, extracting the call graph, etc, you can get via tracing already (sys.settrace, https://docs.python.org/3/library/sys.html#sys.settrace https://docs.python.org/3/library/sys.html#sys.settrace).
And I would argue, the other stated use cases are maybe interesting to play around with, but nothing you really would want in production (I suppose).
Some of the other use cases, you can also achieve by module import hooks and rewriting the AST. (E.g. see how PyTest rewrites the assertion AST to produce nice error messages: https://github.com/pytest-dev/pytest/blob/main/src/_pytest/assertion/rewrite.py https://github.com/pytest-dev/pytest/blob/main/src/_pytest/a...)
- stabbles 2y agothe pytest example screams for @assert as a macro, if only the language supported it
- zem 2y agopytype (https://github.com/google/pytype https://github.com/google/pytype) is based on symbolic interpretation of python bytecode, but with the data stack storing types rather than values. it works very well and has been running in production within google forever. the nice thing about writing a bytecode rather than an AST interpreter is that you can leverage a lot of the work the python compiler does, and work with the resulting simplified code.