On Mar 12, 2012, at 8:38 AM, Marvin Humphrey wrote: >> +1 for this. > > -0, provided that we run this test as part of the community release prep > extended tests, as we do with running test_valgrind. -1 if this test will > never be run.
A better plan is to not ship that test. Put it in MANIFEST.SKIP. That way it is always run in dev, but never in a shipping release. I use this approach for my Pod spelling tests, because other systems have different dictionaries. Best, David
