Re: re.search (works)|(doesn't work) depending on for loop order

On Mar 22, 5:03 pm, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > En Sat, 22 Mar 2008 17:27:49 -0300, sgharvey <[EMAIL PROTECTED]> > escribi�: > Take a look at ConfigObjhttp://pypi.python.org/pypi/ConfigObj/ Thanks for the pointer; I'll check it out. > I'm not sure you can process a config fil

Re: re.search (works)|(doesn't work) depending on for loop order

En Sat, 22 Mar 2008 17:27:49 -0300, sgharvey <[EMAIL PROTECTED]> escribi�: > ... and by works, I mean works like I expect it to. > > I'm writing my own cheesy config.ini parser because ConfigParser > doesn't preserve case or order of sections, or order of options w/in > sections. Take a look at

Re: re.search (works)|(doesn't work) depending on for loop order

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 sgharvey wrote: > ... and by works, I mean works like I expect it to. > > I'm writing my own cheesy config.ini parser because ConfigParser > doesn't preserve case or order of sections, or order of options w/in > sections. > > What's confusing me is t

Re: re.search (works)|(doesn't work) depending on for loop order

On Mar 23, 7:27 am, sgharvey <[EMAIL PROTECTED]> wrote: > ... and by works, I mean works like I expect it to. You haven't told us what you expect it to do. In any case, your subject heading indicates that the problem is 99.999% likely to be in your logic -- the converse would require the result of

Re: re.search (works)|(doesn't work) depending on for loop order

On Mar 23, 8:21 am, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote: > On Sat, 22 Mar 2008 13:27:49 -0700, sgharvey wrote: > > ... and by works, I mean works like I expect it to. > > > I'm writing my own cheesy config.ini parser because ConfigParser > > doesn't preserve case or order of sections

Re: re.search (works)|(doesn't work) depending on for loop order

On Sat, 22 Mar 2008 13:27:49 -0700, sgharvey wrote: > ... and by works, I mean works like I expect it to. > > I'm writing my own cheesy config.ini parser because ConfigParser > doesn't preserve case or order of sections, or order of options w/in > sections. > > What's confusing me is this: >

re.search (works)|(doesn't work) depending on for loop order

... and by works, I mean works like I expect it to. I'm writing my own cheesy config.ini parser because ConfigParser doesn't preserve case or order of sections, or order of options w/in sections. What's confusing me is this: If I try matching every line to one pattern at a time, all the patter