On Fri, May 23, 2014 at 10:17 AM, Eric Snow <ericsnowcurrently@gmail.com>wrote:
On Fri, May 23, 2014 at 10:49 AM, Guido van Rossum <guido@python.org> wrote:
Looking at my own (frequent) use of coverage.py, I would be totally fine if disabling peephole optimization only affected my app's code, and kept using the precompiled stdlib. (How exactly this would work is left as an exercise for the reader.)
Would it be a problem if .pyc files weren't generated or used (a la -B or PYTHONDONTWRITEBYTECODE) when you ran coverage?
In first approximation that would probably be okay, although it would make coverage even slower. I was envisioning something where it would still use, but not write, pyc files for the stdlib or site-packages, because the code in whose coverage I am interested is puny compared to the stdlib code it imports. -- --Guido van Rossum (python.org/~guido)