En Wed, 27 Jun 2007 01:35:27 -0300, O.R.Senthil Kumaran
<[EMAIL PROTECTED]> escribió:
> * Gabriel Genellina <[EMAIL PROTECTED]> [2007-06-25 22:26:47]:
>
>> And how would you detect a multiline value?
>> Because it is not a section nor looks like a new option?
>>
>> I'd try using this:
>>
>> if n
* Gabriel Genellina <[EMAIL PROTECTED]> [2007-06-25 22:26:47]:
> And how would you detect a multiline value?
> Because it is not a section nor looks like a new option?
>
> > I can guess, this portion in the _read function will require change,
> > any change to this affects the whole of parsing. :
En Mon, 25 Jun 2007 11:06:04 -0300, Phoe6 <[EMAIL PROTECTED]> escribió:
> I took the approach of Subclassing ConfigParser to support multiline
> values without leading white-spaces, but am struct at which position
> in _read I should modify to accomodate the non-leading whitespace
> based multilin
Hi,
Am starting a new thread as I fear the old thread which more than a
week old can go unnoticed.
Sorry for the multiple mails.
I took the approach of Subclassing ConfigParser to support multiline
values without leading white-spaces, but am struct at which position
in _read I should modify to acc
