Re: [Configobj-develop] validate() always returns True

[Jim C. <jac...@ma...>]

Actually that appears to be the only bug, replacing "DEFAULT" with
"default" (and replacing print with pprint) yields:

{'CHANNELS': True,
 'default': {'FOOBAR': True,
             'JUNK': VdtTypeError('the value "foobar" is of the wrong
             type.',)}}

(this is with github configobj in Python 2.7).

-Jim


On Tue, Apr 29, 2014, at 10:42 AM, Jim Crowell wrote:
> Started crawling through it with the debugger, found one "feature"
> already: the word DEFAULT appears to have some special, undocumented
> significance (configobj.py from github, line 2301). Got to leave it for
> a while now.
> 
> -Jim
> 
> On Mon, Apr 28, 2014, at 04:46 PM, Jim Crowell wrote:
> > 
> > It appears not to like capital letters as the field names, when I change
> > e.g. DEFAULT to default and so on, it works.
> > 
> > -Jim C.
> > 
> > > Date: Mon, 28 Apr 2014 13:22:39 -0700
> > > From: Mario Aranha <ma...@se...>
> > > Subject: Re: [Configobj-develop] validate() always returns True
> > > To: con...@li...
> > > Message-ID: <535...@se...>
> > > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > > 
> > > If I change the config file:
> > > JUNK = "foobar"
> > > validate still returns True even though the spec file says JUNK is an 
> > > integer.
> > > I also tried with unrepr=True parameter to configObj().