| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
| |
that happens. This silences a noisome exception during the test suite.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the C tracer.
|
| |
|
|
|
|
| |
apparent.
|
|
|
|
| |
have been.
|
| |
|
|
|
|
| |
coverage is started.
|
|
|
|
| |
the process.
|
|
|
|
| |
user. Finishes, but does not fix, issue #93.
|
| |
|
| |
|
|
|
|
| |
it, I hope without introducing too much more new code. Fixes #85.
|
|
|
|
| |
results of should_trace since <<changeset a480f40d1fa4>>
|
| |
|
|
|
|
| |
in subprocesses.
|
| |
|
|
|
|
| |
(had to be sure to stop coverage if check_coverage threw an exception).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
value throughout.
|
|
|
|
| |
form more like it will be consumed. Also should reduce the amount of work the tracers have to do.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
problems. Also, all commands should at least take -h.
|
|
|
|
| |
screwing us up. Now the Python trace function is simpler, with no variability of registered trace function. Fixes bugs #12 and #13.
|
|
|
|
| |
the differences in 2.x and 3.x scoping rules don't change the results of the test. Also, some commented-out logging of the trace machinery that helped me find the problem. Now all tests pass on Python 3.1!
|
|
|
|
| |
function: no pyexpat specifics, and py 2.3 still uses C trace function.
|
|
|
|
| |
tracer there.
|
| |
|