[Python-ideas] Incorporating something like byteplay into the stdlib

[Yury Selivanov]

On 2016-02-12 5:38 PM, Andrew Barnert wrote:
> Assuming I'm not imagining all that, why are people demanding that I provide a rationale for why we should add bytecode optimizers, or telling me that adding bytecode optimizers isn't going to help FAT Python, etc.?
>
> My proposal is that if we add bytecode optimizers, we should make it possible to write them. I don't need to justify that "if". If nobody things we should add bytecode optimizers, not even the author of the PEP that suggests them, then the answer is simple: just remove them from the PEP, and then my proposal becomes void.

Perhaps I and other people don't understand the "if we add bytecode 
optimizers, we should make it possible to write them" part.

I don't expect to see more than 1 or 2 optimizers out there. Writing a 
bytecode optimizer that can yield significant speedups is an extremely 
challenging task.

Adding a lot of new functionality to the stdlib *just* for those few 
optimizers doesn't make a lot of sense.  Moreover, having such tools in 
the stdlib, might cause people to start using them for things other than 
optimization -- something I don't like at all.  We already have import 
hooks, AST etc for most of such purposes.

Yury