Tim provided a correct-looking answer, albeit somewhat
complex, as it doesn't reuse the logic in the ConfigParser.
It didn't start out very complex, but it was so easy to make it a
bit more robust with such a scant few lines of code that I went
ahead. The original just looked like
options
On approximately 12/2/2008 3:22 PM, came the following characters from
the keyboard of Chris Rebert:
On Tue, Dec 2, 2008 at 2:51 PM, Glenn Linderman <[EMAIL PROTECTED]> wrote:
On approximately 12/2/2008 1:31 PM, came the following characters from the
keyboard of Chris Rebert:
On Tue, De
On Tue, Dec 2, 2008 at 2:51 PM, Glenn Linderman <[EMAIL PROTECTED]> wrote:
> On approximately 12/2/2008 1:31 PM, came the following characters from the
> keyboard of Chris Rebert:
>>
>> On Tue, Dec 2, 2008 at 1:18 PM, RON BRENNAN <[EMAIL PROTECTED]>
>> wrote:
>>
>>>
>>> Hello,
>>>
>>> I have a very
On approximately 12/2/2008 1:31 PM, came the following characters from
the keyboard of Chris Rebert:
On Tue, Dec 2, 2008 at 1:18 PM, RON BRENNAN <[EMAIL PROTECTED]> wrote:
Hello,
I have a very simple ini file that I needs parsed. What is the best way I
can parse an ini file that doesn't inc
I have a very simple ini file that I needs parsed. What is the best way I can
parse an ini file that doesn't include sections?
As in:
person=tall
height=small
shoes=big
Thats it. Can anyone help me?
The built-in ConfigParser module assumes at least one INI-style
section, which if it
On Tue, Dec 2, 2008 at 1:18 PM, RON BRENNAN <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a very simple ini file that I needs parsed. What is the best way I
> can parse an ini file that doesn't include sections?
>
> As in:
>
Since it appears that ConfigParser requires at least one section
header,
