[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Daniel Rall <dlr_at_finemaltcoding.com>
Date: 2003-03-07 07:44:16 CET

How strict should I be conforming svn_config to Python's ConfigParser
API? Some differences which I see in the current implementation as I
write config-test.c:

1) [DEFAULT] section isn't handled (should provide default values for
all other sections)

2) Variable substitution isn't handled (duh)

3) __name__ option isn't handled (should default to the name of the
section)

#2 sees like the main target, but I was curious if I should bother
implementing #1 and #3. It would allow us to just point to the
ConfigParser documentation for our interface contract, but would also
result in a slightly more complex implementation.

http://subversion.tigris.org/issues/show_bug.cgi?id=1165

-- 
Daniel Rall <dlr@finemaltcoding.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 7 07:44:50 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.