delta/python-coveragepy-git.git/coverage/pytracer.py, branch coverage-4.3.4

Jython doesn't have useful co_code or f_lasti

2017-01-13T12:31:57+00:00

When nesting tracers, don't restart on the wrong thread

2017-01-02T16:12:33+00:00

The PyPy-specific test for atexit/gettrace are also PyPy-version-specific...

2016-12-31T14:48:34+00:00

Don't warn about trace=None on PyPy at shutdown

2016-12-30T17:30:09+00:00

PyPy clears the trace function before calling atexit functions.  So when we
check if the trace function is changed, don't warn in that specific case.

--HG--
extra : amend_source : a4e946f94b9b84d351a9e112a7eea6a3337bacf1

A thread tweak suggested in #245

2016-05-08T02:15:48+00:00

Entry arcs now use the negative first line of the code object instead of -1.

2016-03-02T12:05:27+00:00

OMG, sometimes the hardest problems have simple solutions. Now metacoverage works with the Python tracer.

2015-08-30T12:55:03+00:00

Too many things named "arcs". Rename the booleans.

2015-08-08T11:00:52+00:00

Add license mention to the top of all files. #313.

2015-07-24T14:43:46+00:00

Fix branch coverage for yield statements. #308 #324

2015-04-20T16:15:37+00:00

Turns out the "call" and "return" trace events are really "start frame" and
"end frame".  They happen not only when functions are entered and left, but
when generators yield and resume.  We aren't interested in arcs into and out
of yield statements, so the trace functions look more closely to see what's
really happening, and record an arc in human-friendly terms.

Thanks for Mickie Betz for pushing on this bug, although her code is no
longer here. :(