On Thu, Jun 26, 2008 at 12:33 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > Guido van Rossum schrieb: > >>>> Ok, then we're back to there being no supported way to write tests that >>>> need to >>>> intercept warnings. Twisted has already suffered from this (JP reports >>>> that >>>> Twisted's assertWarns is broken in 2.6), and I doubt it's alone. >>>> >>>> So I guess I am filing a bug after all... :) >>> >>> Yeah - Brett's correct that everything under "test.test_support" should >>> really be formally undocumented. It's mostly a place for code that >>> reflects >>> "things we do a lot in our unit tests and are tired of repeating" rather >>> than "this is a good API that we want to support forever and encourage >>> other >>> people to use". >> >> I still have a big problem with this attitude. If it's valuable enough >> to share between our tests, it should be properly written for reuse >> and documented. A collection of hacks remains a collection of hacks. >> We can do better. > > Since this is part of Benjamin's project, we will make sure that the > test_support that emerges from it will be properly documented, stable > and usable.
I'm assuming however that Benjamin's project will land in 2.7 or 3.1, right? If he's going to be refactoring tests all summer there's no way that can be merged into the trunk and the py3k branch right before the final release. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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
