Problem writing python tests without installing

[Robert Lupton the Good <rhl at astro dot princeton dot edu>]

When running the testsuite, the python files that are sourced are apparently e.g.
	gdb/testsuite/../data-directory/python/gdb/printing.py
rather than
	gdb/python/lib/gdb/printing.py
although the binary is as expected gdb/gdb

The files appear to be installed by "make install".  This is another manifestation of the problem that you cannot apparently work on the gdb python code without first installing it (away from it's cvs home -- but that can be faked with a link...)

Is there a proper way to work around this?

				R

P.S. I wasted a lot of time on this... the final trick was 
	runtest -v -v -v
and
	gdb_test_no_output "python import gdb.printing" 
	gdb_test_no_output "python raise RuntimeError(gdb.printing.__file__)" 
to get the path.  Sigh.