> Fantastic the doctests are very nice.
I'm glad you like'em. :-)
> Unfortunately all those test functions need rewriting - as they need to
> not just test values (return True/False) but transform values as well.
No problem, now that the tests work and are in-context, it should be easy
to update and use them to check the changes as they are done.
> I've done the changes to the Validator object that implement this on my
> PDA !
Great, so attach them to an email and I'll commit them. ;-)
> I'd also thought of ripping out all the regex stuff and rethinking it.
>
> The example functions as they stand aren't much use I don't think.
> Written by Mark Andrews. I've rewritten them for basic data types -
> more complex tests can be built on top of these !
I reworked some of them too, as you may have seen.
> We can discuss which of the other tests are worth keeping when I return.
>
> Do what you want to configreader.py. (Within reason). My project for my
> time away is to start on the docs for ConfigObj. (Using my PDA *grin*).
I'll convert the tests in ConfigObj to doctest format too, as soon as I can.
> It's probably best to leave validate.py for now - until you can see the
> basic data types I've kept (do we really *need* to test complex
> numbers !) - and we decide which of the other tests are worth keeping
> (and changing so they work with the new system).
Ok, I'll leave it alone, until your changes show up.
--
Nicola Larosa - ni...@te...
Adding things just because you can leads to monstrosities like Common LISP,
PL/I, Algol 68 and Perl 6. Adding features only when they add functionality
(or better yet, by removing restrictions) leads to jewels like Python,
Scheme and Eiffel. -- Mike Meyer, comp.lang.python, April 2005
|
