You cannot post messages because only members can post, and you are not currently a member.
Description:
This is the discussion list for LEPL, a Parser Library for Python.
Note: If you do not have a Google account you can join this list by sending an email to lepl-subscribe [at] googlegroups [dot] com.
|
|
|
IMPORTANT: End of Project
|
| |
I am making something official that has been obvious in practice for a while
now: the LEPL project is now dead.
This means:
- There will be no more major releases
- I will only fix small issues
- I will feel less obligation to respond to requests for support
- I will place some kind fo notice to this effect on the main site and update... more »
|
|
|
Detection of ambiguous grammar
|
| |
Dear LEPL experts,
In trying to find a good parser for Python to implement a rather
complex grammar. I already know that Pyparsing will dot detect the
ambiguities of my grammar, and so far only ANTLR does. But as I am
trying to avoid having to compile the grammar before I can use it, I
am now looking at LEPL, which seems quite powerful.... more »
|
|
|
Upgrade from LEPL 4.4.0 to 5.0.0 => out of memory
|
| |
Hi! I've been using LEPL for my more complex needs for quite a while now and I love it! So, first of all, a big thank you to Andrew and other contributors, for the excellent and invaluable project that is LEPL. My grammar has problem (probably some left-recursion issue somewere). With LEPL 4.4.0 the problem didn't manifest itself, however since LEPL 5.0.0 for... more »
|
|
|
Changes to the introduction
|
| |
Just read through the docs, looks pretty awesome. A couple things about the introduction: - In intro-1 there is a link to the FAQ at the end of "Creating Numbers" about >> vs >, it would be nice if this link was instead in the note at the end of "Adding Values" after the basic explanation of the what the... more »
|
|
|
rfc3696 URL validation memory leak?
|
| |
Hi all
I'd like to use the LEPL rfc3696 module for URL/URI validation. But
when I added validation into my application (which processes RDF data
with many URLs, some of them broken), its memory usage jumped through
the roof. It seems to me that LEPL leaks a significant amount of
memory when validating URLs.... more »
|
|
|
Output or serialize ASTs to XML, JSON?
|
| |
I am curious if LEPL has direct support for serializing ASTs into a corresponding textual representation, such as XML. If not, how would one go about producing same. I'd like to run a series of XPath queries against the ASTs. e.g. to query a repository of source code for usage patterns, best or forbidden... more »
|
|
|
Run-length encoded input?
|
| |
Hi, I hope someone can help me with this somewhat newb-ish question. I'm trying to write a parser for a binary syntax that uses run-length encoding. In essence, it looks like the following: lepl.UnsignedInteger & ~lepl.Literal(':') & lepl.Any()[LENGTH] Where LENGTH is the result of the matching UnsignedInteger. However I can... more »
|
|
|
5.1.0 Released
|
| |
This is a very small change from 5.0.2, but breaks a public API (changing Repeat very slightly) so it seemed worth a middle version number. I've added the Reduce() matcher which does a reduce (or fold) over the results from another matcher. This is the generalisation necessary to make String() work in a consistent way across different types.... more »
|
|
|
serialization/pickling of matchers
|
| |
Hi, I was wondering if it was possible to save a matcher for later sessions, to avoid recompiling them after an environment reset. Is it possible? I tried pickle and it did not work.
|
|
|
