Re: [1165] strictness of svn_config to Python's ConfigParser API

=?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
...
> Hm, my experience (and understanding of the docs) is different; perheps
> this did change between 2.0 and 2.2. I guess it's not that hard to
> implement this behaviour (in fact, it would help you with the variable
> expansion semantics), so +1 if you care to do it.

Okay, will do.

> >The description of [DEFAULT] doesn't match what I'm seeing. The
> >Python docs don't describe it in detail, so there's bound to be
> >confusion -- perhaps I misunderstand?
>
> Yes, there seems to be some confusion. I'd say go ahead and reproduce
> the behaviour you showed above. Luckily, we've thrown out the only use
> of [default] we had till now.
>
> We do have one big difference, though -- our section and option names
> are case-insensitive. That's intentional, and I thing we should keep it.

Experimentation shows me that all section names (including the
[DEFAULT] section) for a ConfigParser configuration file are case
sensitive, so this certinaly is a difference. However, option names
appear to be case-insensitive, which is consistent with svn_config.

Anyone have issues with retaining this difference? Since we're
already planning on retaining other differences, I'm ambivalent.

-- 
Daniel Rall <dlr@finemaltcoding.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org