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

Re: Python package situation

Path	csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!feeds.phibee-telecom.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From	Andrey Rahmatullin <wrar@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Python package situation
Date	Tue, 16 Feb 2021 22:20:02 +0100
Message-ID	<BJfVg-8iG-3@gated-at.bofh.it> (permalink)
References	<BHoJk-6G2-7@gated-at.bofh.it> <BHulH-1CA-3@gated-at.bofh.it> <BJ4Gu-1w5-3@gated-at.bofh.it> <BJfse-7SD-7@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Tue Feb 16 21:13:34 2021
Old-Return-Path	<wrar@debian.org>
X-Amavis-Spam-Status	No, score=-12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -3.5
Dkim-Signature	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wrar.name; s=20160710; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:From:Sender:Reply-To:Subject:Date: Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=xBwIL/kxD0nX9wBzSRM9N3JURglxkvWhD5FDTGcZ4xs=; b=x+ZPA0tonPtuuOKfXEeIuvPLwf G/EhYVv1d6zZofvhbqxv7WniLKxz6vIt1qYtrt5vyyjIvgNmB6qUEJp8bPgXg3NrMib11PouUCdst G6Iih4r9Vk0sd0ctbgkh7xs3Rl47ajKdmQsCl3H/fNF13ZBMrzpyoCAXbLMfe49FW/gE=;
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K4Rl8DFQShzMkdiT"
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/19007
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/YCw1boMi/ReDbwOx@belkar.wrar.name
Approved	robomod@news.nic.it
Lines	52
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 17 Feb 2021 02:13:18 +0500
X-Original-Message-ID	<YCw1boMi/ReDbwOx@belkar.wrar.name>
X-Original-References	<20210211181234.GA4829@silverpine> <5c9a9365-20b9-c600-638c-6c74a024779a@debian.org> <s0g2iu$9h1$1@ciao.gmane.io> <YCwvhRb2pWtT91JG@fama>
Xref	csiph.com linux.debian.maint.python:13224

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Feb 16, 2021 at 09:48:05PM +0100, Martin wrote:
> > I *wish* I could
> > just install everything via the Debian Packaging System, but the reality for
> > most relevant Python packages is very different: packages are either
> > outdated or do not exist in Debian
> 
> Are you talking about many packages? Or only some, that are
> difficult to package? Can you give an example?
Are you asking about testing or stable? Because for stable the "packages
are either outdated or do not exist" situation is somewhat expected and
testing is not that interesting case, though even in testing we may have a
lot of outdated packages.

> At my job, we were always able to stay with Debian packages, or
> I just packaged the missing pieces, but maybe our use case is
> not that advanced.
Surely you use only a subset of modules while other people may need a
different subset, and ability to make and upload new or updated packages,
unavailable for most Debian Python users, is definitely helpful.

-- 
WBR, wRAR

Thread

upstream python concerns, python3-full package for bullseye Elana Hashman <ehashman@debian.org> - 2021-02-11 19:20 +0100
  Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-11 19:30 +0100
    Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-16 05:30 +0100
      Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-16 17:30 +0100
  Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 01:20 +0100
    Re: upstream python concerns, python3-full package for bullseye stefanor@debian.org - 2021-02-12 01:50 +0100
      Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 09:20 +0100
        Re: upstream python concerns, python3-full package for bullseye Raphael Hertzog <hertzog@debian.org> - 2021-02-12 09:40 +0100
          Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-12 10:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Martin <debacle@debian.org> - 2021-02-12 11:30 +0100
            Re: upstream python concerns, python3-full package for bullseye Christian Kastner <ckk@debian.org> - 2021-02-12 13:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Julien Palard <julien@palard.fr> - 2021-02-12 14:10 +0100
              Re: upstream python concerns, python3-full package for bullseye Matthias Klose <doko@debian.org> - 2021-02-12 17:40 +0100
              Re: upstream python concerns, python3-full package for bullseye Thomas Goirand <zigo@debian.org> - 2021-02-13 23:10 +0100
            Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-12 21:20 +0100
        Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-12 21:00 +0100
          Re: upstream python concerns, python3-full package for bullseye Michael Kesper <mkesper@schokokeks.org> - 2021-02-12 21:50 +0100
      Re: upstream python concerns, python3-full package for bullseye Tristan Seligmann <mithrandi@mithrandi.net> - 2021-02-12 10:30 +0100
        Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 10:50 +0100
          Re: upstream python concerns, python3-full package for bullseye Jonathan Carter <jcc@debian.org> - 2021-02-12 11:40 +0100
            Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 12:10 +0100
          Re: upstream python concerns, python3-full package for bullseye Simon McVittie <smcv@debian.org> - 2021-02-12 15:20 +0100
            Re: upstream python concerns, python3-full package for bullseye Andrius Merkys <merkys@debian.org> - 2021-02-12 17:00 +0100
              Re: upstream python concerns, python3-full package for bullseye Valentin Vidic <vvidic@debian.org> - 2021-02-12 17:20 +0100
    Re: upstream python concerns, python3-full package for bullseye Michael Kesper <mkesper@schokokeks.org> - 2021-02-12 11:00 +0100
    Re: upstream python concerns, python3-full package for bullseye Jeremy Stanley <fungi@yuggoth.org> - 2021-02-12 18:00 +0100
    Re: upstream python concerns, python3-full package for bullseye Bastian Venthur <venthur@debian.org> - 2021-02-16 10:20 +0100
      Re: upstream python concerns, python3-full package for bullseye Stefano Rivera <stefanor@debian.org> - 2021-02-16 19:30 +0100
        Re: upstream python concerns, python3-full package for bullseye Jeremy Stanley <fungi@yuggoth.org> - 2021-02-16 20:20 +0100
      Python package situation Martin <debacle@debian.org> - 2021-02-16 21:50 +0100
        Re: Python package situation Andrey Rahmatullin <wrar@debian.org> - 2021-02-16 22:20 +0100
          Re: Python package situation Martin <debacle@debian.org> - 2021-02-16 23:20 +0100
          Re: Python package situation Brian May <bam@debian.org> - 2021-02-17 02:10 +0100
            Re: Python package situation Andrey Rahmatullin <wrar@debian.org> - 2021-02-17 08:00 +0100
            Re: Python package situation Raphael Hertzog <hertzog@debian.org> - 2021-02-17 10:30 +0100

csiph-web