Groups > linux.debian.maint.python > #12178

Re: name change: python-lark-parser -> python-lark

From	Peter Wienemann <fossdev@posteo.de>
Newsgroups	linux.debian.maint.python, linux.debian.bugs.dist
Subject	Re: name change: python-lark-parser -> python-lark
Date	2019-12-30 20:30 +0100
Message-ID	<zj8TM-4Qk-9@gated-at.bofh.it> (permalink)
References	(1 earlier) <zibAm-v5-1@gated-at.bofh.it> <yN8yJ-5G1-7@gated-at.bofh.it> <ziP4J-8km-9@gated-at.bofh.it> <zj5VT-31m-5@gated-at.bofh.it> <zj6Ih-3ww-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Hi Simon,

thanks for your helpful input.

On 30.12.19 18:04, Simon McVittie wrote:
> There are two options:
> 
> * If "lark" on PyPI is a dead project, or otherwise something that is never
>   going to be useful to package in Debian for some reason, then perhaps it's
>   safe for the lark parser to claim the python3-lark name.

The last commit happened six years ago. It might be dead but I am not sure.

> * Otherwise, if its PyPI name is lark-parser, then I would personally
>   recommend asking the upstream developer to rename the module you import
>   to lark_parser (or maybe larkparser if that's preferred), and packaging
>   it as python3-lark-parser (or python3-larkparser), optionally with
>   compatibility glue to make "import lark" continue to work (which might not
>   get packaged in Debian).

I opened a corresponding issue:

https://github.com/lark-parser/lark/issues/505

Peter

Thread

Re: name change: python-lark-parser -> python-lark Peter Wienemann <fossdev@posteo.de> - 2019-12-30 17:20 +0100
  Re: name change: python-lark-parser -> python-lark Simon McVittie <smcv@debian.org> - 2019-12-30 18:20 +0100
    Re: name change: python-lark-parser -> python-lark Peter Wienemann <fossdev@posteo.de> - 2019-12-30 20:30 +0100
    Re: name change: python-lark-parser -> python-lark Thomas Andrejak <thomas.andrejak@gmail.com> - 2019-12-30 22:20 +0100

csiph-web