MegaIng

I am getting completely different errors. Are you sure the patch in the post is the *only* difference between master and your local? One the one hand, missing dependencies (`pytest`,...

Can you provide reproduction steps from a completely empty environment, i.e. preferably including creating a new `venv`?

No, there is not builtin way to deal with this, you will need to write custom stuff on a case by case basis. [hypothesmith](https://github.com/Zac-HD/hypothesmith) does this by more or less...

You could try to write a general system that goes back a token, tests if the lexing still does the same stuff with the new token and otherwise inserts an...

Seems to me like it's a langchain (or less likely, PyInstaller) issue, not a lark issue. Did you open an issue there?

Didn't we previously try something into this direction? Wasn't the problem that is ambiguous what should be ignored on the borders between rules when they have different ignore sets? I.e....

Note that my project [`interegular`](https://github.com/MegaIng/interegular) tries quite a bit harder to match stdlib's `re` syntax and I am currently reworking it to use `greenery.fsm` in the background, so that might...

lark has facilities for this, namely `import_paths`. If "project A" means an importable package, you can use the `FromPackageLoader` helper class: ```py from lark.load_grammar import FromPackageLoader Lark(... , import_paths=[FromPackageLoader('A', [''])...

`node.data` *isn't* part of the input, but of the grammar. Use `node.meta` instead. @erezsh We really need to change it back so that `Tree` doesn't take Token, but just their...

@munching We aren't talking about your issue directly. If lark behaved correctly, you would have gotten an `AttributeError` from accessing those names on `.data`, which probably would have clued you...