[Python-Dev] Code coverage tool updated
tim.peters at gmail.com
Fri Nov 12 05:29:03 CET 2004
> Using regrtest.py's tracing option instead of trace.py gives better
> results (see http://styx.livinglogic.de/~walter/brokentrace2.txt):
> 656 covered modules (including a strange /tmp/tmp6ccfd4/t5/string.py)
test_pkg.py creates the weird string.py. Don't know why.
> There seems to be something wrong with the way trace.py starts
> the script.
> BTW, I'd like to have an option the specify the coverdir in regrtest.py,
> as now finding the coverage file when you have the name of the Python
> file is more complicated. But I guess this has to wait until 2.4 is
> out the door.
I don't know anything about this, but there's no reason to avoid
changing regrtest.py just because 2.4 is in beta. The arguments to
regrtest.py aren't documented, and it's an internal module to help us
test Python anyway. So if you can do better 2.4 testing by changing
it now, change it now.
More information about the Python-Dev