Open GoogleCodeExporter opened 8 years ago
interesting. I'll have to check it out. Is it possible to somehow compact it?
It's already a fairly long function...is there a more succinct way of doing
this? Thanks for your input!
Original comment by tobyro...@gmail.com
on 22 Aug 2012 at 6:27
A friend of mine had a go at condensing the logic - it's still the same basic
algorithm (I don't think that can be made much simpler), but is now a little
shorter. Not sure if that helps, but it's a bit easier to follow now as well:
https://github.com/gfxmonk/piep/blob/master/piep/main.py#L147
Original comment by gfxm...@gmail.com
on 22 Aug 2012 at 10:14
ok, cool. we'll check that out. thanks for working on this.
Original comment by tobyro...@gmail.com
on 5 Sep 2012 at 6:46
I like the compactness of the second example. Do you guys have some examples of
how pyp fails with real world text? I see your unit tests, but we haven't
really encountered that kind of parsing here.
Thanks!
Original comment by tobyro...@gmail.com
on 1 Feb 2013 at 5:32
I'm afraid it's been too long, I didn't keep any examples that failed (although
I definitely encountered one in regular, that's how I found the bug). I assumed
the unit tests were sufficient to show that the code was buggy...
Original comment by gfxm...@gmail.com
on 1 Feb 2013 at 11:33
Original issue reported on code.google.com by
gfxm...@gmail.com
on 16 Aug 2012 at 12:35