Basil
Simple Parser Library. Describe the syntax in a JSON file.
Features:
- Easy to use
- Syntax description in JSON, no complicated notation
- Transform parse tree to any type you want
- Helpful messages when parser runs into errors
Limitations:
- Does not detect conflicts
- Not designed for speed
How to install
# If you use pip
pip install basil-parser==0.4.3
# If you use PDM
pdm install basil-parser==0.4.3
How to use
If you're unfamiliar with parsers, please read the section on lingo used below.
1. Create the syntax JSON for your language.
See this example, which describes the syntax of a subset of JSON.
The JSON should be an object with the following values:
- a
keyword_tokensobject, where the name is the token type insnake_caseand the value is a regex for tokens of this type. - a
regular_tokensobject, similar to keyword tokens, except names can't overlap. Keyword tokens are considered higher priority. - a
filtered_tokensarray of strings. Lists token types that should be ignored. This is sometimes useful for getting rid of whitespace. - a
nodesobject, where the name is the node type inTITLE_CASEand the value is an expression describing which configuration of child (tokens and nodes) is allowed, using this syntax:expr | expr: choose one of the expressions(expr expr): combine expressions into oneexpr*: repeat expression 0 or more timesexpr+: repeat expression 1 or more timesexpr?: expression is optional
- a
root_nodestring value, indicating the node type of the root of the parse tree.
2. Parse and transform
In your python code load the JSON with the FileParser. You only need to load the FileParser once, regardless of how many files are parsed, because it doesn't change any state when parsing files.
The output of the parser is hard to work with, so we transform it into something more workable. To allow the user to transform nodes and tokens into any type, a transformer function must be implemented with signatures as in the below example.
For a concrete working example, see how parse_text_and_transform() is used in basil_json_loads() in this example.
from pathlib import Path
from basil.file_parser import FileParser
parser = FileParser(Path("path/to/your/syntax.json"))
transformed = parser.parse_text_and_transform(
"code in your language",
node_type="your root_node",
node_transformer=node_transformer,
token_transformer=token_transformer,
)
TRANSFORMED_TYPE = ... # Some union of types
def node_transformer(
node_type: str, children: List[TRANSFORMED_TYPE | Token]
) -> TRANSFORMED_TYPE:
# Translate to a TRANSFORMED_TYPE value based on the node type and it's children
...
def token_transformer(token: Token) -> TRANSFORMED_TYPE | Token:
# Translate to TRANSFORMED_TYPE based on token.type or token.value
# It is also possible to return `token` as is.
...
3. Test
As usual, testing is optional but recommended. Regexes are tricky. The parser may not match things they way you expect. It is a good idea to test at least all nodes with some inputs that should match and some that should not. See this file as an example.
Lingo used
Tokenizer
Chops a file into a list of tokens, which are effectively small chunks of text. When a file is tokenized successfully, every character in the file is part of exactly one token. When the values of all tokens are pasted together, we get the original file.
Parser
Translates a list of tokens into a parse-tree consisting of tokens and nodes.
Token
A token is a piece of text (value) that has a certain token type. This is usually a single word or a sequence of characters indicating the start, end (such as brackets) or separation (such as comma's) of other parts of the file. Tokens are described by a regex in the syntax JSON.
Node
Contains a list of children Used to group tokens into a block of code, or data. The types of nodes and tokens that are accepted for a node type are described in the syntax JSON.
Name
This project was called "Basil" because many people call their parser library parsley.
License
This software is released under the MIT license.
Metadata
Release files for basil-parser 0.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| basil_parser-0.4.3.tar.gz | 42.9 kB | Without provenance | Details for basil_parser-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| basil_parser-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for basil_parser-0.4.3-py3-none-any.whl |
Total release size: 91.1 kB
Release files / basil_parser-0.4.3.tar.gz
| Download URL | basil_parser-0.4.3.tar.gz |
|---|---|
| Size | 42.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2835fda231bc7a58eec60bbd607d004187836414456c24d63f756b3f085f3797
|
|
BLAKE2b-256 checksum How to use checksums |
9d89ca736a62b53069dbf28531b69cf614f577a1318cf33c58a17fc70c257c6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.10.4 CPython/3.10.2
|
Release files / basil_parser-0.4.3-py3-none-any.whl
| Download URL | basil_parser-0.4.3-py3-none-any.whl |
|---|---|
| Size | 48.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26e64f01aeb2d7c8d26266e71b79ebecb6857579e4fdcbd479350470059c79a4
|
|
BLAKE2b-256 checksum How to use checksums |
ef5da966eda9cb6fb6051dca3c3abfa9bff5ac606801a92bfc4d8bc5057cc616
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.10.4 CPython/3.10.2
|
Security for basil-parser 0.4.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.