Re: [Configobj-develop] ConfigObj Tests

[Nicola L. <ni...@te...>]

> Seeing as I'm going to do a new release of ConfigObj I might as well
> move the tests into a separate file.

Yes, sorry for not having got round to doing it myself, as promised. :-(


> For the sake of consistency I suppose I have to move *all* the tests.

Not necessarily.


> If there are any that serve as particularly concise examples I might
> leave them in place, but the tests have grown quite unwieldy now.

Indeed, one or two tests could be usefully left in each docstring as usage
examples.


> Removing the tests and some of the text will shrink configobj.py by
> quite a way.

Definitely.

-- 
Nicola Larosa - http://www.tekNico.net/

I have not heard of any of the rather significant core of Python language
and library developers saying "hey, this Ruby thing really solves a lot
of problems we've been having in Python, I'm going over there." Instead,
they write PEPs (Python Enhancement Proposals) and morph the language to
incorporate the good features. -- Bruce Eckel, December 2005