On 2019-04-24 18:48, Brett Cannon wrote:
Since bytecode is a CPython-specific implementaiton detail I don't know
if it makes sense to enshrine an assembler for it in the stdlib (if you
were to ask me today if I thought the dis module belonged in the stdlib
I would probably say "no", but I also know not everyone agrees with that
view :) .
The dis module can help you understand what's happening below the
surface; it's just that what happens below the surface is
implementation-specific and can change between releases...
On Wed, Apr 24, 2019 at 10:36 AM Batuhan Osman Taşkaya
<batuhanosmantask...@gmail.com <mailto:batuhanosmantask...@gmail.com>>
wrote:
Hello,
Currently it is hard to assemble cpython bytecode without help of
3rd party libraries (like: vstinner/bytecode). I'm proposing an
assembler to standard library and an API to cpython's peephole
optimizer. Also an interface like `ast.NodeVisitor` and
`ast.NodeTransformer` for bytecode objects will may be handy.
It would help if you are doing;
- Runtime patching
- Specific optimizations at bytecode level
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
