Re: [Rest2web-develop] None and Defaults

[Nicola L. <ni...@te...>]

>> I'm cool with the "None" string, by itself, always meaning the None value,
>> like True or False, but not restricted to one check type. Maybe we should
>> take out that "lower" method, though.

> I'm not - ConfigObj shouldn't change the type without the programmer
> specifying it.

Good point.


> Don't forget the value is set by the *user* - not the programmer.
> ConfigObj should only convert type if the programmer says. None
> shouldn't be an acceptable value for every check - maybe it *isn't* an
> acceptable value (what if the programmer really does want an integer
> there - he expects validate to tell him).

Yes, actually None is a value of type NoneType. Hadn't realized that
before, was thinking of it as an amorphous no-type-every-type non-value.


> This means that someone's program will break because a user enters
> 'None' as a string value. It ought to be possible to have 'None' as a
> string value in a config file without our program converting it to
> another type.

Another good point.


> I thought the point was to catch defaults ?

Yes, it was, but then I incautiously adventured into YAGNI land. ;-)


> My proposed (and currently committed) solution allows the programmer to
> specify that None is ok (by using default='None'), which makes the value
> explicitly (user sets value as 'None')

I don't think the user may explicitly set a None value, now, but it may as
well be that way.


> and implicitly (user omits value altogether) optional.

That's probably enough.


> I'm fine with removing the 'lower'.

So be it. Sorry for the confusion.

-- 
Nicola Larosa - ni...@te...

Python is the best thing I've seen in 30 years of computing for
pedogogical and productive purposes. Only when I want speed do I
see a need for something else. -- Chuck Allison, June 2005