From: Skip Montanaro <skip@pobox.com>
Date: Tue, 6 May 2003 16:17:27 +0000 (+0000)
Subject: add Guido's reasoning behind running all tests twice
X-Git-Tag: v2.3c1~837
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c9803ab855f7c96278952627dec44899b78d109a;p=python

add Guido's reasoning behind running all tests twice
---

diff --git a/Makefile.pre.in b/Makefile.pre.in
index 207798eff4..843c50fd4b 100644
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -514,6 +514,13 @@ $(LIBRARY_OBJS) $(MODOBJS) Modules/$(MAINOBJ): $(PYTHON_HEADERS)
 ######################################################################
 
 # Test the interpreter (twice, once without .pyc files, once with)
+# In the past, we've had problems where bugs in the marshalling or
+# elsewhere caused bytecode read from .pyc files to behave differently
+# than bytecode generated directly from a .py source file.  Sometimes
+# the bytecode read from a .pyc file had the bug, somtimes the directly
+# generated bytecode.  This is sometimes a very shy bug needing a lot of
+# sample data.
+
 TESTOPTS=	-l
 TESTPROG=	$(srcdir)/Lib/test/regrtest.py
 TESTPYTHON=	$(RUNSHARED) ./$(BUILDPYTHON) -E -tt