On Thu, Jul 8, 2010 at 3:29 PM, Antoine Pitrou <solip...@pitrou.net> wrote: > On Fri, 9 Jul 2010 00:59:02 +1000 > Nick Coghlan <ncogh...@gmail.com> wrote: .. > I don't really like the proliferation of module test helpers, it only > makes things confusing and forces you to switch between more files in > your editor. By contrast, the subclassing solution is simple, explicit > and obvious. > And would require a lot of tedious and error prone work to retrofit existing tests. Since we don't have meta regression tests, there is no obvious way to assure that retrofitting does not change the tests. Note that test_pickle uses both the subclassing solution *and* a helper pickletester module because this neatly separates maulti-implementation machinery from the actual test definitions.
> (I also wonder what problem this subthread is trying to solve at all. The problem is to find a simple solution that will allow running existing unit tests written for a C extension on both the original extension and the added pure python equivalent. When the existing tests were developed over many years and have 100+ test cases, this is not as easy task as it would be if you wrote your tests from scratch. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
