<!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">
Jesse Keating wrote:
<blockquote cite="mid:20071002110223.5cfb5e45@redhat.com" type="cite">
<pre wrap="">On Tue, 02 Oct 2007 14:47:06 +0200
Oliver Falk <a class="moz-txt-link-rfc2396E" href="mailto:oliver@linux-kernel.at"><oliver@linux-kernel.at></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">OK, that might be the better fix. But doesn't it make sense
ConfigParser also allows int as values? I mean any kind of number
(int, float, complex) could be handled as string...
</pre>
</blockquote>
<pre wrap=""><!---->
I know not the history of ConfigParser and why it's only strings. I
suspect it's because ConfigParser's primary usage is to parse config
files, and in a file it may be non-obvious how to mark something as an
int/float rather than a string. The reason pungi uses ConfigParser is
that prior to using kickstart files we had our own config files. I'm
not entirely happy with ConfigParser, but it'd be something of an
overhaul to switch to some other config system, and not one I was
willing to make at this point. Maybe during F9...
</pre>
</blockquote>
You can take a look at the config classes in yum (yum/config.py) it let
you define different kind of options types.<br>
<br>
Tim<br>
</body>
</html>