Re: [Configobj-develop] [PATCH] add indent_size was: add indent_size + patch (sort of)

[Jorge V. <jor...@gm...>]

On 8/6/06, Michael Foord <fuz...@vo...> wrote:
>
> Jorge Vargas wrote:
> > bah I'm so stupid.... I forgot setuptools takes eggs before files, so
> > my code was actually calling the official release.
> >
> > this patch works.
> >
> > by the way I think you can delete DEFAULT_INDENT_TYPE and set it
> > inside the OPTION_DEFAULTS that will solve the readonly NOTE from the
> > __all__
> >
> > again great work keep it up.
> Hello Jorge,
>
> Thanks for the compliments and the patch Jorge. :-)
>
> My main concern with ConfigObj at the moment is that the number of
> features and options seems to grow with every release. This actually
> makes it harder for people to use ConfigObj, rather than easier.


actually I didn't find any fiction getting into it, I wrote a inifile by
hand in order to understand what I wanted then I google for configObj, open
the first link read and started writting the code, then make my patch. when
I read the options sections on
http://www.voidspace.org.uk/python/configobj.html#options I found that I
could use them all if it was needed.

I think the key is here

Simple is better than complex.
Complex is better than complicated.

yes ConfigObj is complex with all those options. but if you don't need them
you don't even have to worry about them

as shown here
http://www.voidspace.org.uk/python/configobj.html#reading-a-config-file and
here http://www.voidspace.org.uk/python/configobj.html#writing-a-config-file

so in this case ConfigObj is simple.

and as the first paragraph in this message, how can something that you get
up, running and enhance(although a small feature) in an afternoon be
complicated?