configobj-develop

[Configobj-develop] ConfigObj Tests

[Fuzzyman <fuz...@vo...>]

Hello,

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

For the sake of consistency I suppose I have to move *all* the tests. If 
there are any that serve as particularly concise examples I might leave 
them in place, but the tests have grown quite unwieldy now.

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

All the best,

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

[Configobj-develop] ConfigObj Tests

[Fuzzyman <fuz...@vo...>]

Hello all,

I've split the ConfigObj tests into a separate file, and the 
changelog/todo etc into a text file.

There are some example tests left in configobj.py.

This has brought configobj.py down from 3700 lines to 2100 lines. (123k 
to 74k)

I'll upload these to SVN tonight (4.3.0alpha4). Once I've done the doc 
changes, which are quite extensive, I'll do the release. This might take 
another week or so.

Currently the copy mode of validate *doesn't* handle the 'DEFAULT' 
sections. validate doesn't touch them so that you *can* use string 
interpolation in your configspec files. I can't think of a clean way 
round this, so I'm not proposing to fix it for the moment. If this 
causes anyone problems I/we will have to find the best way round it. 
Maybe validation could just copy any DEFAULT sections without passing 
them through any validator checks ?

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml

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

Re: [Configobj-develop] ConfigObj Tests

[Fuzzyman <fuz...@vo...>]

Nicola Larosa wrote:
>> 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. :-(
>
>   

Not a problem, it's an easy job.
>   
>> For the sake of consistency I suppose I have to move *all* the tests.
>>     
>
> Not necessarily.
>   
I'm copying *all* the tests into a file called ``configobj_test.py``. 
I'm leaving a few useful ones in configobj.py as well.

>> 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.
>
>
>   

There won't be any doctest stuff in configobj.py, so they are now 
examples only.
>> Removing the tests and some of the text will shrink configobj.py by
>> quite a way.
>>     
>
> Definitely.

I've removed some of the text. I've left the ISSUES and CHANGELOG in as 
it is useful to keep these *in* the file. That way someone who just has 
configobj.py still has some information about it.

I suppose the CHANGELOG doesn't contain that much information, so I 
wouldn't be averse to moving that into a separate text file if you 
thought it was better. (About 400 odd lines.)

Fuzzyman
http://www.voidspace.org.uk/python/index.shtml