summaryrefslogtreecommitdiffstats
path: root/Lib
diff options
context:
space:
mode:
authorNeal Norwitz <nnorwitz@gmail.com>2006-02-28 20:40:50 (GMT)
committerNeal Norwitz <nnorwitz@gmail.com>2006-02-28 20:40:50 (GMT)
commitcd8ca8092f5ccdafe80e81488baf867041afc2b1 (patch)
treed49fb877b4192d78b65ebad9b265e0781a27ffff /Lib
parent84ef21c033c4b2177db6498a9d1ecbaa7050fe90 (diff)
downloadcpython-cd8ca8092f5ccdafe80e81488baf867041afc2b1.zip
cpython-cd8ca8092f5ccdafe80e81488baf867041afc2b1.tar.gz
cpython-cd8ca8092f5ccdafe80e81488baf867041afc2b1.tar.bz2
Add a note about removing the file once the bug is fixed
Diffstat (limited to 'Lib')
-rw-r--r--Lib/test/leakers/README.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Lib/test/leakers/README.txt b/Lib/test/leakers/README.txt
index 801ed95..69ee35a 100644
--- a/Lib/test/leakers/README.txt
+++ b/Lib/test/leakers/README.txt
@@ -2,7 +2,8 @@ This directory contains test cases that are known to leak references.
The idea is that you can import these modules while in the interpreter
and call the leak function repeatedly. This will only be helpful if
the interpreter was built in debug mode. If the total ref count
-doesn't increase, the bug has been fixed.
+doesn't increase, the bug has been fixed and the file should be removed
+from the repository.
Here's an example interpreter session for test_gestalt which still leaks: