[TIP] cleanUp for unittest
holger at merlinux.eu
Fri Apr 3 13:21:43 PDT 2009
On Fri, Apr 03, 2009 at 21:07 +0100, Michael Foord wrote:
> holger krekel wrote:
>> As guido says the standard library is for dead code and at least i
>> don't consider supporting better ways for
>> functional and integration testing with Python to be a
>> dead-code project :)
> His word was stable, not dead.
he said stable and that in biology stable means dead.
> We should be conservative, and with a new release every 18 months
> standard library modules *can't* grow rapidly, but we will continue to
> see unittest grow and adapt to testing needs and useful patterns.
>> but your mileage may vary and for me it's fine if you want to care
>> for adding some more refined cleanUp semantics to unittest.py. Maybe
>> the suggestion in my other post about getresources() is
>> applicable in this case.
>>> Looking for examples in the standard library would be a good idea. To
>>> be honest it seems such a clean and simple idea I'm surprised at the
>>> pushback so may not pursue it. But still, plenty of other fish to
>> tons of fish everywhere, indeed :) cheers,
Metaprogramming, Python, Testing: http://tetamap.wordpress.com
Python, PyPy, pytest contracting: http://merlinux.eu
More information about the testing-in-python