On 28/12/15 00:41, Guido van Rossum wrote:
Can you show the diffs you have so far? Somebody's got to look at your code.
Sounds like it's not a well-known symptom then. I agree, but that
Somebody should be me (initially, at least) - I don't want to waste
other people's time if I made a silly m
You can look at https://docs.python.org/devguide/compiler.html to see if
you missed something.
As for the _frozen_importlib problem, that typically manifests itself when
you have invalid bytecode (that module is frozen bytecode that gets
compiled into the interpreter and is the first bit of Python
Can you show the diffs you have so far? Somebody's got to look at your code.
--Guido (mobile)
On Dec 27, 2015 16:51, "Erik" wrote:
> Thanks for your help so far (I'm experimenting with the peephole optimizer
> - hence my question before as I was trying to work out how to know what the
> small in
Thanks for your help so far (I'm experimenting with the peephole
optimizer - hence my question before as I was trying to work out how to
know what the small integer hard-coded offsets should be when looking
ahead in the bytecode).
I've successfully added a new opcode (generated by the optimiz
On 12/26/15 10:19 PM, Nick Coghlan wrote:
On 27 December 2015 at 12:23, Guido van Rossum wrote:
On Sat, Dec 26, 2015 at 6:06 PM, Brett Cannon wrote:
Ned also neglected to mention his byterun project which is a pure Python
implementation of the CPython eval loop: https://github.com/nedbat/by
