#26 Wrong ParseError in some special cases

[Eike Welk]

Under certain special conditions a parser does not recognize legitimate input and instead raises a parse error.

To provoke the error one needs:
- to use setResultsName frequently.
- an own class to replace ParseResult. This class needs a __getitem__ method.
- some bad luck.

The attached script demonstrates the bug.

This a very obscure bug, and it can be quite easily worked around. So this bug does not need a high priority, however it confused me quite a bit.

[Eike Welk]

Script to demonstrate error.

[Paul McGuire]

Obscure, perhaps, but fixable nonetheless.

Thanks for posting this, I'll have a fixed version in SVN shortly.

-- Paul

[SourceForge Robot]

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).