<!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 text="#000000" bgcolor="#ffffff">
On 01/08/2010 03:57 PM, r0g wrote:
<blockquote cite="mid:hi7h4o$rcd$1@speranza.aioe.org" type="cite">
<pre wrap="">Chris Rebert wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Thu, Jan 7, 2010 at 10:19 AM, Peter <a class="moz-txt-link-rfc2396E" href="mailto:vmail@mycircuit.org"><vmail@mycircuit.org></a> wrote:
<snip>
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The .ini file is the simpliest solution, at least from the user point of
view, no need to learn any python syntax.
</pre>
</blockquote>
<pre wrap="">I am speaking from the point of view of a python programmer, and I find the
.ini restrictions not necessarily simple, for example when dealing with
structured data (I suppose it is trivial to specify a dictionnary or a list
for the purpose of my request) For example, configuration files for the
logging module get unwieldy when you specify several loggers , handlers,
formatters etc, because you have to break down structured data ( objects )
to name,value pairs.
</pre>
</blockquote>
<pre wrap=""><snip>
</pre>
<blockquote type="cite">
<pre wrap="">So what is the "worshipped" approach, when you need more than name=value
pairs ?
</pre>
</blockquote>
<pre wrap="">
JSON is one option: <a class="moz-txt-link-freetext" href="http://docs.python.org/library/json.html">http://docs.python.org/library/json.html</a>
Cheers,
Chris
--
<a class="moz-txt-link-freetext" href="http://blog.rebertia.com">http://blog.rebertia.com</a>
</pre>
</blockquote>
<pre wrap="">
Yes, JSON is rapidly becoming a standard for stuff like this as it's
widely portable and less bulky than XML. It's the native format for
couchdb too which is nice if you want to replicate and share the
contents of your documents.
Roger.
</pre>
</blockquote>
Excellent, thanks , have to check that out. Any experience with <a
href="http://yaml.org/">yaml</a> ?<br>
Peter<br>
</body>
</html>