Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


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

Re: Separate lib and executable packages?

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Gordon Ball <gordon@chronitis.net>
Newsgroups linux.debian.maint.python
Subject Re: Separate lib and executable packages?
Date Tue, 11 Feb 2020 11:00:01 +0100
Message-ID <zyAuJ-79N-3@gated-at.bofh.it> (permalink)
References <zxaj0-1TJ-3@gated-at.bofh.it> <zxemB-4AP-1@gated-at.bofh.it> <zxoOZ-4ki-1@gated-at.bofh.it> <zxEqJ-5G3-9@gated-at.bofh.it> <zxEK6-656-9@gated-at.bofh.it>
X-Mailbox-Line From debian-python-request@lists.debian.org Tue Feb 11 09:52:46 2020
Old-Return-Path <gordon@chronitis.net>
X-Amavis-Spam-Status No, score=-7.2 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_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_FROM_MX=-3.1; rate: -4.6
Dkim-Signature v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=chronitis.net; s=mythic-beasts-k1; h=Subject:To:From:Date; bh=4tUkrHjjy2/bT/h50d1PRqXkHaJZU5ubbbm975BxBtA=; b=n1HX8R2tbGQ5XdzSj0u2L24KdH TK0W4OSgz9fbpSfKSCAXGbJf063RB0or3Q7HW3l0D9Mt+CrQt4nX3Os4GbtlgoM/x81t7nn7DbfF2 6NhenV93J/Uss3tVOkiFqBzCXIENj9mbl1cAlqXfbk9LvQ24QofB04wFN7t784v/Xle+sEhTl+57k b7ZwQJ6dnbqa1LC6a2pecfWQiHtmTNUL06KSIqqbMz2xysTW6mqQjNxTKtzrOkRtr4XpShd+/9YCR kk+zxKvjxW9vjGgOdYrOostZ8hiMPwdEb8wP2UNSKi6EpGRicuIV1Cp6ej5Sm3XwIQQ2Y8tosAzPC SMCZWc8A==;
MIME-Version 1.0
Content-Type text/plain; charset=utf-8
Content-Disposition inline
Content-Transfer-Encoding 8bit
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17919
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20200211095226.uaeldoqrrrxhix2m@emissary.chronitis.net
Approved robomod@news.nic.it
Lines 41
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Cc Scott Kitterman <debian@kitterman.com>, debian-python <debian-python@lists.debian.org>
X-Original-Date Tue, 11 Feb 2020 09:52:26 +0000
X-Original-Message-ID <20200211095226.uaeldoqrrrxhix2m@emissary.chronitis.net>
X-Original-References <20200207113600.fzlk2wzks4hwazfd@emissary.chronitis.net> <20200207155946.GA385407@mapreri.org> <05B3F2AA-564D-4F32-BF03-99C3E646C5F8@kitterman.com> <20200208195054.upmidqwwx2stj6gw@emissary.chronitis.net> <CAOO6c=yy1=daaU5Eh7vLveEwJp5Za43maVHQtXcc8U6=RZ0dAA@mail.gmail.com>
Xref csiph.com linux.debian.maint.python:12293

Show key headers only | View raw


On Sat, Feb 08, 2020 at 08:54:27PM +0100, Ondrej Novy wrote:
> Hi,
> 
> so 8. 2. 2020 v 20:51 odesílatel Gordon Ball <gordon@chronitis.net> napsal:
> 
> > Perhaps this is worth making an explicit recommendation for new packages
> > of this type, given that anything new _should_ be python3-only and we
> >
> 
> and what about pypy- prefix?

That's a good point.

Probably not many packages are likely to provide pypy{,3} invoking binaries
(ipython is probably actually a good candidate here) and so it probably
counts as an exceptional case which can reasonably bypass a recommendation.

I suppose you could:

 * Not ship any executables which invoke pypy. For pypy3, that appears
   to be the case today (nothing in /usr/bin using pypy3 except the
   interpreter itself).
 * Ship the library and python3 executable together (possibly with a
   Provides: for the executable), and the pypy3 executable in a
   separate package (since the library itself presumably
   doesn't want to depend on pypy3, and might need to depend on
   pypy-specific library packages). This saves 1 binary package but
   seems inconsistent. The actual implementation could be picked with
   update-alternatives.
 * Ship library, python3 executable and pypy3 executable separately.
   This seems more consistent but generates an extra binary package.

This is probably a good case to consider in this thread because ipython
and ipykernel are probably reasonable cases where a pypy-specialised
executable might make sense, and ipython at least depends only on
pure-python modules which work out-of-the-box with pypy.

> 
> -- 
> Best regards
>  Ondřej Nový

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Separate lib and executable packages? Gordon Ball <gordon@chronitis.net> - 2020-02-07 12:50 +0100
  Re: Separate lib and executable packages? Ondrej Novy <novy@ondrej.org> - 2020-02-07 13:50 +0100
  Re: Separate lib and executable packages? Mattia Rizzolo <mattia@debian.org> - 2020-02-07 17:10 +0100
    Re: Separate lib and executable packages? Scott Kitterman <debian@kitterman.com> - 2020-02-08 04:20 +0100
      Re: Separate lib and executable packages? Ondrej Novy <novy@ondrej.org> - 2020-02-08 14:00 +0100
        Re: Separate lib and executable packages? Scott Kitterman <debian@kitterman.com> - 2020-02-08 15:30 +0100
      Re: Separate lib and executable packages? Gordon Ball <gordon@chronitis.net> - 2020-02-08 21:00 +0100
        Re: Separate lib and executable packages? Ondrej Novy <novy@ondrej.org> - 2020-02-08 21:20 +0100
          Re: Separate lib and executable packages? Gordon Ball <gordon@chronitis.net> - 2020-02-11 11:00 +0100
        Re: Separate lib and executable packages? Scott Kitterman <debian@kitterman.com> - 2020-02-09 04:10 +0100

csiph-web