On Mon, May 11, 2015 at 10:01 AM, BartC <b...@freeuk.com> wrote:
> (1) It has an extra argument ('code'), in addition to any normal arguments
> of func (0 in this case)Which might well push execution down the unoptimized code path. Also, ISTR that Steven's original timeit runs tacked on a standalone "eval ; ..." to the function call case, so the LOAD_GLOBAL bytecode would have been done in the function call case as well. He was, I think, doing what he could to make the two cases as nearly identical as he could. Skip -- https://mail.python.org/mailman/listinfo/python-list
