Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
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: Mon, 30 Dec 2019 20:30:02 +0100
Message-ID: <zj8TM-4Qk-9@gated-at.bofh.it>
References: <yN8yJ-5G1-7@gated-at.bofh.it> <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>
X-Original-To: Simon McVittie <smcv@debian.org>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Mon Dec 30 19:29:11 2019
Old-Return-Path: <fossdev@posteo.de>
X-Amavis-Spam-Status: No, score=-9.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1577734138; bh=sH84+Svp57Gzc0KW6FPN9q66pwwNWiSPkx1HIFPyi8U=; h=Subject:To:Cc:From:Date:From; b=hW6ezBciagbKQA6qUtEtLV+bhikuvUmCfdyYbiJKty6CwVJ8yt04imzYzdRYib/hp CerVAVNlT0TG3Ne++HUApfchnzMnQ+zG2GBIyaPdc+kfn4/qF85f8xqgVYU54d4vm8 VMioNRVU2wKiaN29Ab5TtFoGrs0kdf8tYTrf6e1yIro/JXl+TI6MJpvjdM/ZOHQwc7 zIEBXRl4m9XF8H+f6CZ3YyQpDsY4qMAW81ZiPPGKff+WpY3wObcRt7WYSiFgSSzKQw 25O2MzSUWobY3ehsv2nXzRlDkSNfXKXlxSDPfVQtrlJ4TUlX8mMZE8EdUlDVlU14p0 5Hr+PX06CJWTg==
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/17783
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/328a3275-c3aa-fb80-b151-a21c7d3338e1@posteo.de
Approved: robomod@news.nic.it
Lines: 25
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Cc: Thomas Andrejak <thomas.andrejak@gmail.com>, debian-python@lists.debian.org, 941657@bugs.debian.org
X-Original-Date: Mon, 30 Dec 2019 20:28:56 +0100
X-Original-Message-ID: <328a3275-c3aa-fb80-b151-a21c7d3338e1@posteo.de>
X-Original-References: <157010587458.28402.9959108423212056872.reportbug@emil.localdomain> <c4e73c9d-6bec-9b6a-ecd1-468ec2b1a483@posteo.de> <157010587458.28402.9959108423212056872.reportbug@emil.localdomain> <CABjmheNQvOZ7nzndmu=-uP8LMg+c38TvKnT5bFNA5DCzg3ZX1w@mail.gmail.com> <bf44d793-79fa-c183-0e06-9a45fd585e2b@posteo.de> <20191230170451.GA453619@espresso.pseudorandom.co.uk>
Xref: csiph.com linux.debian.maint.python:12178 linux.debian.bugs.dist:989198

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