Made compatibility with lark ≥1.0!#100
Conversation
No, it shouldn't. End users are not supposed to call it. |
|
That branch should be taken only on the machines of the ones building a wheel from source. If it is taken in an installed wheel, it is likely it will error - |
|
Hi @KOLANICH Will you be able to rebase with the master and fix PR checks? |
already done.
Works for me locally ( |
|
https://github.com/amplify-education/python-hcl2/actions/runs/3794008621/jobs/6451675562
|
|
@htorianik will help with it |
|
Under "not reporting" I meant this: https://github.com/amplify-education/python-hcl2/actions/runs/3794168036/jobs/6451977387 No exception, no failed test name, no details, just something somewhere has failed. |
…the versions of lark up to 1.0.
… routines for that. + satisfyed `pylint` about this file.
…ause lark by now generates the code not passing `mypy` checks. And `mypy` seems to be having a bug that its ignore settings sometimes don't work.
|
Done. 🎉🎉🎉 I guess you may want to report the bugs in |
|
2BH I'm not sure how to behave about that and if the parsers generated by |
I just wanted to highlight it |
Compatibility was broken by lark-parser/lark@6bb9e8a
|
Tested. |
|
@KOLANICH Nice work! Thank you for your contribution! |
|
In theory we can support both |
|
In my opinion, it's not needed |
No description provided.