Re: [Pyparsing] Memory issues with 2.0.6

[Paul M. <pt...@au...>]

There were two logic changes made in 2.0.6:

- a bug in Or (operator ^) was fixed which handles the case where the
longest match fails because of a parse action raising an exception, but an
alternative shorter match succeeds; previously this would erroneously fail
to match, but now successfully returns the shorter alternative match

- a bug in Each (operator &) was fixed that would erroneously return
multiple matches of Optional expressions

There was one additional change that introduced a bug that only affects
users with unicode in their expressions.

If your grammar has complex expressions (especially recursive expressions)
using ^ or & operators, these new bugfixes may be the problem.

Andrea, I'll try to take a look at the PyContracts code that you posted and
see if any glaring areas jump out. will, I hope these descriptions will give
you some clues where to start looking in your grammar.  I can also post some
before-after snippets that you can patch into your versions of pyparsing and
rerun your tests.

-- Paul


-----Original Message-----
From: Andrea Censi [mailto:an...@cd...] 
Sent: Thursday, November 19, 2015 7:03 PM
To: Will McGugan <wil...@gm...>
Cc: Pyp...@li...
Subject: Re: [Pyparsing] Memory issues with 2.0.6

> starts eating memory until the process is killed by the OS.

Me too!

I have been wondering why all of a sudden my Travis unit tests were failing,
with the processes being killed.
<snip>


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus