|
From: Nicola L. <ni...@te...> - 2006-03-07 06:56:41
|
> Nicola (ConfigObj co-developer) - the last three support queries I've > had for ConfigObj have all been to do with empty values. It seems that a > lot of people are using ConfigObj to parse ini files created elsewhere. > > IIRC the empty value *is* part of the normal ini spec. (A later version > of ConfigObj 3 supported them.) Would you object to me extending > ConfigObj to read empty values ? > > A logical counterpart to this is an additional option (default False) > allowing you to specify that ConfigObj should write out empty values in > place of the empty string. > > What do you think ? I don't know about the INI specs, but it seems a reasonable requirement, and since there are real use cases, I'd say go ahead. -- Nicola Larosa - http://www.tekNico.net/ It will always be true that people that drive slower than me are morons, and people that drive faster than me are idiots. :) -- Matthew Carlisle on Slashdot, December 2005 |