Author pitrou
Recipients asvetlov, benjamin.peterson, charettes, ezio.melotti, fabioz, gvanrossum, matthewlmcclure, matthewlmcclure-gmail, meador.inge, michael.foord, pitrou, python-dev, r.david.murray, rhettinger, terry.reedy, tim.peters, tomwardill
Date 2013-09-14.14:31:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379169114.23.0.524806840169.issue11798@psf.upfronthosting.co.za>
In-reply-to
Content
> I'd rather not propagate more options all the way through, especially 
> as this is some thing that should be decided by the test framework and 
> is unlikely to be something you want to turn on and off per test run
> (which is what command line options are for). Frameworks that want to 
> disable this behaviour should use a TestSuite that overrides
> _removeAtIndex.

That sounds like a completely disproportionate solution. Why would you have to override the TestSuite class just to change an option and restore old behaviour? Why don't you simply expose the cleanup flag on TestSuite instances?
History
Date User Action Args
2013-09-14 14:31:54pitrousetrecipients: + pitrou, gvanrossum, tim.peters, rhettinger, terry.reedy, fabioz, benjamin.peterson, ezio.melotti, r.david.murray, michael.foord, matthewlmcclure, asvetlov, meador.inge, python-dev, tomwardill, matthewlmcclure-gmail, charettes
2013-09-14 14:31:54pitrousetmessageid: <1379169114.23.0.524806840169.issue11798@psf.upfronthosting.co.za>
2013-09-14 14:31:54pitroulinkissue11798 messages
2013-09-14 14:31:53pitroucreate