|
From: Patrick T. <pat...@gm...> - 2012-08-19 11:37:56
|
Hi! I'm not sure if it makes much sense to report this here as the list seems more or less dead.. Anyhow, I ran into something nasty with configobj/validate. I think the subject says it all: If your configspec says foo = string(default=None) and your config reads foo = bar, baz validation using cfg.validate(Validator()) does not fail and afterwards cfg.foo foes not contain "bar, baz" but ["bar", "baz"]. Apparently one can force lists using foo = force_list in the spec, bot one cannot force *not* list, which from my perspective would be the logical behaviour of spec "string". cheers, /p |