|
From: Fuzzyman <fuz...@vo...> - 2006-03-07 10:20:01
|
Nicola Larosa wrote: >>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. > > I'll implement this and do an update. The new option/attribute to be called ``write_empty_values``. All the best, Fuzzyman http://www.voidspace.org.uk/python/index.shtml |