Use modern lark parser#140
Open
marlamb wants to merge 1 commit into
Open
Conversation
The `lark_parser` package has been superseded by `lark`. As both use the same namespace (`lark`), using `lark_parser` can result in a collusion, if users of the ELM client use `lark` as well within their dependency tree. Then the runtime behavior becomes installation-order dependent. As the usages of lark within the library seem to work fine with the modern lark as well, using the modern package should be preferred. Signed-off-by: Martin Lambertsen <github@lambertsen.one>
marlamb
force-pushed
the
feature/use-modern-lark-parser
branch
from
July 13, 2026 13:36
b86941a to
15474be
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
lark_parserpackage has been superseded bylark. As both use thesame namespace (
lark), usinglark_parsercan result in a collusion,if users of the ELM client use
larkas well within their dependencytree. Then the runtime behavior becomes installation-order dependent.
As the usages of
larkwithin the library seem to work fine with themodern
larkas well, using the modern package should be preferred.