Produce more helpful errors.
E.g. show which variant was tried to be parsed and failed.

Currently no error is produced at runtime when accidentally passing str instead of bytes, for example when using Literal('foo') instead of Literal(b'foo'), but parsing does not work. This should either raise an error or be handled gracefully (e.g. by encoding the string to bytes with ascii encoding).

It seems i cannot do some elementary parsing

is it me ? or ?

#!/bin/env python

import asyncio
from bite import Parser, CharacterSet, Combine, Group, Literal, parse_bytes, Suppress, Opt, ZeroOrMore

upper_case= CharacterSet(b'ABCDEFGHIJKLMNOPQRSTUVWXZ')

lower_case= CharacterSet(b'abcdefghijklmnopqrstuvwxz')

upper_case= CharacterSet(bytes(range(ord(b'A'),1+ord(b'Z'))))
lower_case= CharacterSet(bytes(range(ord(b'a'),1+ord(b'z'))))

digit = CharacterSet(b'0123456789')
digits = digit[1, ...]

integer = Combine(digits)
letter=lower_case|upper_case
char=letter|digit

ident = Combine(letter + (char | '_')[0, ...])

obj = parse_bytes( ident, "un")
result = asyncio.run( obj )
print(result

Input: 'un'
^ location of error

The naming of parse nodes (from the parsers) is somewhat inconsistent and random at the moment. This should be made consistent. Also, names should not try to represent the sub-parse-tree, but make it easy to find specific nodes. Thus, it might be sufficient to just use the type of parser.

• Quoted strings (incl. quote removal)
• parenthesized lists
• nested expressions

I think it would be a bit simpler to track a single extent (as 2-tuple) than two separate values in the ParseNodes.

Enable useful debug output that clarifies why and how parsing is failing.

When the buffer is a bytearray (instead of bytes) the wrong location will be marked when an UnmetExpectationError is printed.