Consider chasing down the name `lark` for pip.

Sadly, the name lark is taken on pip, and it appears to be used a bit. However, I think there is a really good chance that 99.9% of those are people wrongly trying to install lark-parser.

This is especially evident when you look at libraries.io attempt to figure out dependents. Half is recognized, other half is wrongly depending on lark instead of lark-parser. Exactly one is is correctly dependent, by the same author as lark itself @voidfiles.

If you look at the github analysis the picture doesn’t really change.

@voidfiles is also ignoring an issue about this since half a year, despite being active on github.

We can try to use PEP 541 if @voidfiles doesn’t answer here, but we would have to first try to reach him via email, then shoot an issue at pypi-support.

[erezsh]

I’m happy to announce it is now possible to pip install lark!

Thanks you @voidfiles for being so helpful and understanding! I will add a small thank you note in the next release, if that’s alright with you.

[voidfiles]

K, should I’ve invited you. Sorry that I didn’t see this earlier.