I believe I commented it out when we were trying to get the buildbots
green before releasing 2.6. (The fact that regrtest.py trips over it
does suggest there are legitimate reasons for calling doctest.testmod()
more than once in a single test suite though)

It looked like some debugging code that was accidentally left in to me
(putting random stuff on the screen in a test tool that monitors what is
written to stdout is less than helpful...)

Since 2.5 is only getting security fixes now and later versions don't
suffer from the issue, I'm closing this one as "out of date".