From 140540957dca50165624d227b450934c93da9576 Mon Sep 17 00:00:00 2001 From: Tim Peters <tim.one@comcast.net> Date: Fri, 18 Nov 2005 17:21:19 +0000 Subject: [PATCH] Merge rev 40230 from the 3.6 branch. Testing from a checkout is different than testing from a distribution now. Explain the differences. Removed the business about fiddling PYTHONPATH, because it shouldn't be needed (and isn't for me ;-)). --- README.txt | 22 +++++++--------------- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/README.txt b/README.txt index 69001c47..27ded738 100644 --- a/README.txt +++ b/README.txt @@ -92,12 +92,14 @@ script:: This should now make all of ZODB accessible to your Python programs. -Testing -------- +Testing for Developers +---------------------- + +When working from a ZODB checkout, do an in-place build instead:: -ZODB comes with a large test suite that can be run from the source -directory before ZODB is installed. The simplest way to run the tests -is:: + % python setup.py build_ext -i + +followed by:: % python test.py -v @@ -120,16 +122,6 @@ Running all the tests takes much longer.:: OK -To test the build, first build the externals and add the src dir to -your PYTHONPATH, - - % python setup.py build_ext -i - % export PYTHONPATH=`pwd`/src:$PYTHONPATH - -Then run the test script:: - - % python test.py - History ------- -- 2.30.9