> Note the following issue with ``ValidateParamError`` in validate.py :
>
> Because ``ValidateParamError`` is a subclass of ``ValidateError``,
> it will
> always be trapped by ConfigObj as a failed check. Should we get
> ConfigObj to
> propagate this error ? (as it is a programmer error and not a failed
> check)
>
> The easiest way to get round it is to either create a new error class
> that isn't a subclass of ``ValidateError`` - or use a built in Exception.
The first solution is best, and meaningful too. It's a different class of
Errors, after all. We should have more of them. ;-)
> By the way - thanks for your work on the docs.
You're welcome.
--
Nicola Larosa - ni...@te...
Any fool can talk, but it takes a wise man to listen.
-- AccUser on Slashdot, July 2005
|
