<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Vinay Sajip wrote:
<blockquote cite="midloom.20060130T004747-592@post.gmane.org"
type="cite">
<pre wrap="">Fuzzyman <fuzzyman <at> voidspace.org.uk> writes:
</pre>
</blockquote>
Hello Vinjay,
<blockquote cite="midloom.20060130T004747-592@post.gmane.org"
type="cite">
<blockquote type="cite">
<pre wrap="">In the past there has been some discussion about a new module to replace
ConfigParser. Most notably at
<a class="moz-txt-link-freetext"
href="http://wiki.python.org/moin/ConfigParserShootout">http://wiki.python.org/moin/ConfigParserShootout</a>
</pre>
</blockquote>
<pre wrap=""><!---->[snip]
</pre>
<blockquote type="cite">
<pre wrap="">It would be possible to extend to the ConfigObj API to be backwards
compatible with ConfigParser. This would bring the added benefits of
ConfigObj, without needing to add an extra module to the standard library.
Well nearly. ConfigObj supports config file schema with (optional) type
conversion, through a companion module called validate. This could be
included or left as an added option.
Anyway. If this stands a *chance* of acceptance, I'll write the PEP (and
if accepted, do the work - which is not inconsiderable).
</pre>
</blockquote>
<pre wrap=""><!---->
Personally, I'd prefer to have the different candidates in the Shootout be
evaluated and a "winner" picked (I'm not sure who would do this, or when it
would be done). </pre>
</blockquote>
Quite.<br>
<br>
I'm suggesting an alternative that bypasses that tortuous and unlikely
process. ;-)<br>
<blockquote cite="midloom.20060130T004747-592@post.gmane.org"
type="cite">
<pre wrap="">I'll readily declare an interest - I've implemented an
alternative hierarchical config module (which is in no way backward compatible
with ConfigParser), see
<a class="moz-txt-link-freetext"
href="http://www.red-dove.com/python_config.html">http://www.red-dove.com/python_config.html</a>
</pre>
</blockquote>
<br>
I realise that there are several alternative modules available .
Obviously my personal preference is ConfigObj (I'm not unbiased of
course). :-)<br>
<br>
Lack of complexity is the major feature I would tout here - I guess
other people would have different priorities.<br>
<br>
However, this not the only issue. Adding a new module, with a different
API and possibly a different syntax for files, is a recipe for (some)
confusion. Not to mention the difficulty of achieving a consensus on
python-dev. (Again - ;-)<br>
<br>
The resolution I'm suggesting means that people can continue to use
ConfigParser, with major feature enhancements. *Or* they can migrate to
a slightly different API that is easier to use - without needing to
switch between incompatible modules.<br>
<br>
I'm currently adding the ``ConfigParser.get*`` methods to ConfigObj
(user request) and also adding full (straightforward) unicode support
for reading and writing. These changes will be available in a beta
release in the next few days.<br>
<br>
Anyway, debate on the issue is welcomed.<br>
<br>
All the best,<br>
<br>
<br>
Fuzzyman<br>
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/python/configobj.html">http://www.voidspace.org.uk/python/configobj.html</a><br>
<blockquote cite="midloom.20060130T004747-592@post.gmane.org"
type="cite">
<pre wrap="">Regards,
Vinay Sajip
_______________________________________________
Python-Dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Python-Dev@python.org">Python-Dev@python.org</a>
<a class="moz-txt-link-freetext"
href="http://mail.python.org/mailman/listinfo/python-dev">http://mail.python.org/mailman/listinfo/python-dev</a>
Unsubscribe: <a class="moz-txt-link-freetext"
href="http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk">http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk</a>
</pre>
</blockquote>
<br>
</body>
</html>