[bind10-dev] _check_item_spec behavior

[JINMEI Tatuya / 神明達哉]

At Tue, 19 Oct 2010 10:37:57 +0200,
Jelte Jansen <jelte at isc.org> wrote:

> actually, these should be maintained by hand. These are specification of
> modules, i.e. on par with their source code
> 
> > If the specification is actually corrupted, there is a "JSON parse 
> > error" but still many lines of Traceback output that may cause admin to 
> > overlook the actual problem,
> 
> errors in the spec file should be seen as programming errors, admins should
> never ever edit these files. We could look into shortening them (i.e. trying to
> catch them on a somewhat higher level, and raising another exception with its
> contents), but in general I prefer too much information over too little for
> code-level errors

IMO, showing too much information and revealing a native backtrace
(which may cause too much information as a result) are different.  The
former is a matter of how to present errors, and the latter is a
matter of how to handle errors.  Regardless of how much, I believe we
should catch any possible exceptions within our program and handle
them accordingly.

---
JINMEI, Tatuya