id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
387	figleaf confused by python2.5	warner	somebody	"I'm seeing some messed up code-coverage data coming out of 'make
test-figleaf' runs when using python2.5 (since debian/sid recently upgraded).
The results suggest that we don't have as good test coverage as we really do.

The main problem I've seen is with multi-line parenthesis-wrapped
expressions, like this:

{{{
 323.         extra_lease_offset = (self.HEADER_SIZE
 324.                               + 4 * self.LEASE_SIZE
 325.                               + data_length)
}}}

When test-figleaf is run under python2.5, the report says that line 323 is
unexecuted code, line 324 is not code, and line 325 is executed code. Under
python2.4, the report says that line 323 is executed code, and both 324 and
325 are non-code.

The net results are annoying. With python2.4, figleaf reports 820 lines
uncovered out of 12297 lines total (which I think is pretty accurate, with
the exception of the code in allmydata/__init__.py that is just plain weird,
see #109). But the python2.5 results claim 1104 lines uncovered out of 13175
total.

I suspect that a change in the python2.5 tracing output is confusing figleaf.
We've hacked up figleaf in several ways.. perhaps there are some fixes
upstream that we might be able to apply to our local copy.
"	defect	closed	minor	1.7.0	code	1.0.0	wontfix	figleaf coverage testing