GitXplorerGitXplorer
b

persil

public
1 stars
0 forks
0 issues

Commits

List of commits on branch main.
Verified
d674c32c4ab6456ebad94f4c7b4cf9689a7af51f

fix: tests (#5)

bbdura committed 9 months ago
Unverified
bbb117b64823cc73f0e0e51eacca083e041a6552

chore: update changelog

bbdura committed 9 months ago
Unverified
0b3779f7d606c069a13e70e3fec574c238ac930a

chore: bump version to 0.1.0

bbdura committed 9 months ago
Unverified
c2b365ba9d46edab4581db08e242ab7adc4bf8d5

test: stream api

bbdura committed 9 months ago
Unverified
476820e8e0b91cdd76088d8f2dcc4f5783f086c7

docs: update changelog

bbdura committed 9 months ago
Unverified
e20caff01f69ec5f8b7e1ede9e105a332c82e14a

docs: document most methods

bbdura committed 9 months ago

README

The README file for this repository.

Persil

Persil is a pure-python parsing library that draws much (most, let's be honest) of its inspiration from the excellent Parsy library.

Hence the name, "Persil" ([pɛʁ.sil] or [pɛʁ.si]), the French word for parsley -a most questionable pun on Parsy -> Parsley -> Persil, in case anyone missed it.

Like Parsy, Persil is a "monadic parser combinator library for LL(infinity) grammars". As a rough approximation, you can think of Persil as a typed "fork" of Parsy. However, although the APIs are very similar, there are notable differences that you might want to review if you're coming from Parsy.

If you're merely looking for a somewhat type-aware version of Parsy, you may be looking for parsy-stubs. Mypy can use it to infer most of the types, but you'll find that shortcuts had to be taken in many cases.

Getting started

Persil is a pure-Python library. You can install it with pip:

pip install persil

Then, you can play with persil much the same way you would with Parsy, and enjoy the great developer experience that type-hinting brings to Persil.

A basic example

from persil import regex

year = regex(r"\d{4}").map(int)

This example should drive home the point that Persil is heavily inspired by Parsy. The only difference in this particular case is type-safety: the persil version knows that year is a parser that expects a str, and outputs an int.

More complex parsers

Parsy uses generator functions as a most elegant solution to define complex parser.

While you can still use this approach with Persil, you're encouraged to favour the from_streamer decorator:

@from_streamer
def parser(
    stream: Stream[str],
) -> CustomType:
    a = stream(parser_a)
    b = stream(parser_b)
    c = stream(parser_c)

    return CustomType(a, b, c)

The equivalent code, using generate instead (deprecated in Persil):

@generate
def parser() -> Generator[Parser, Any, CustomType]:
    a = yield parser_a
    b = yield parser_b
    c = yield parser_c

    return CustomType(a, b, c)

The main issue with generate is that intermediate parsers cannot be typed, whereas Stream.__call__ plays nice with modern Python tooling like mypy.

Relation with Parsy

First of all, I am not affiliated in any way with the Parsy project.

Rationale

Parsy's last commit is from a year ago at the time of writing. Moreover, although the authors have started some development to propose a typed version of their library, efforts in that area have stalled for two years.

Compatibility with Parsy

Although Persil draws most of its inspiration from Parsy, maintaining a one-for-one equivalence with the latter's API is NOT among Persil's goal.

For those coming from Parsy, here are some notable differences:

  • the Result type is now a union between Ok and Err, which allow for a more type-safe API.
  • Err is its own error: it inherits from Exception and can be raised.
  • Persil introduces the Stream class, a wrapper around the input that can apply parsers sequentially, keeping track of the book-keeping.

Performance tips

Since Persil takes a functional approach, every transformation on a parser produces a new parser. With that in mind, the way you define/use/combine parsers may substantially affect performance.

Consider the following example:

from datetime import datetime

from persil import Stream, from_stream, regex, string


@from_stream
def datetime_parser(stream: Stream[str]) -> datetime:
    year = stream.apply(regex(r"\d{4}").map(int))
    stream.apply(string("/"))
    month = stream.apply(regex(r"\d{2}").map(int))
    stream.apply(string("/"))
    day = stream.apply(regex(r"\d{2}").map(int))
    return datetime(year, month, day)

The resulting datetime_parser will re-create three new regex parsers every time it is run.

A much better alternative:

from datetime import datetime

from persil import Stream, from_stream, regex, string


year_parser = regex(r"\d{4}").map(int)
day_month_parser = regex(r"\d{2}").map(int)
slash_parser = string("/")

@from_stream
def datetime_parser(stream: Stream[str]) -> datetime:
    year = stream.apply(year_parser)
    stream.apply(slash_parser)
    month = stream.apply(day_month_parser)
    stream.apply(slash_parser)
    day = stream.apply(day_month_parser)
    return datetime(year, month, day)

That way, the lower-level parsers are only defined once.