Re: [Pyparsing] Memory issues with 2.0.6

[Andrea C. <an...@cd...>]

> 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.

~

[I also have a case in which a grammar worked (defined as: "parses
string s") in Python 2.7, but doesn't (syntax error with the same
string s) in >=3.3, and the specific errors changed with the latest
update of PyParsing.

http://github.com/AndreaCensi/contracts

So I guess something substantial changed in the latest release.

]


On Thu, Nov 19, 2015 at 7:42 PM, Will McGugan <wil...@gm...> wrote:
> Hi,
>
> My app has a fairly complex grammar to parse expressions. Up to 2.0.5 it
> was working well. But in 2.0.6 it gets stuck parsing and starts eating
> memory until the process is killed by the OS.
>
> I've pinned pyparsing to 2.0.5 for now. I haven't done any debugging yet,
> but I was wondering what had changed since 2.0.5 that could trigger this
> kind of behaviour? Any known bugs?
>
> Thanks in advance,
>
> Will McGugan
> ------------------------------------------------------------------------------
> _______________________________________________
> Pyparsing-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pyparsing-users



-- 
Andrea Censi | http://andrea.caltech.edu | "Not all those who wander are lost."
research scientist @ LIDS / Massachusetts Institute of Technology