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


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

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream

Path csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod
From Gregor Riepl <onitake@gmail.com>
Newsgroups linux.debian.maint.python
Subject Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream
Date Mon, 14 Oct 2019 20:20:01 +0200
Message-ID <yRd6N-6kT-1@gated-at.bofh.it> (permalink)
References <yQZwR-64v-3@gated-at.bofh.it> <yQZwR-64v-1@gated-at.bofh.it> <yR2O6-8hX-3@gated-at.bofh.it>
X-Mailbox-Line From debian-python-request@lists.debian.org Mon Oct 14 18:18:30 2019
Old-Return-Path <onitake@gmail.com>
X-Amavis-Spam-Status No, score=-7.179 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, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -5.5
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=2sM95+JTMeMuQ5QosIq9j+U86B4w/vflDfzIl1DdMms=; b=DkfMfJ9no3gZMYBYNPCD48185ecy83DNPr+f0ubC/UP481ySoVmiRPD/a5HLrVL+ER hjdHC2pOV939cShQ71o/xm7AK8rM5vjVhRy5t7fcqMTCePtlshlN/RbohF3RleZzGpxT ssK/fR0Z++4nedZogNkcMy/YIVepSaqtC3+Mm5s+y7eh0j+/hH/6kXNTyWJIw6plEwVH o3iTYglZBKF+vM710LHZlsCXyo1YVJe9H9lDuyQyL9kGNWDU6oOw07iS85Q05cZnEcHw KdkPwrI2SropTEtLhJrnXxS7c1seJwKVSE/K6TtYRX7KAfqT/esZyMV4ge07IDHtfh39 qHoQ==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=2sM95+JTMeMuQ5QosIq9j+U86B4w/vflDfzIl1DdMms=; b=TQPnRbI4mpc1uBFdo0HVjiPwJ+G9Gx7xK+IFML7MPHRYlIKQbtwNIbpmx7bo2ntNlz PSXy5/oATwFwU5FEqrJAvWrafy/UkBEur5e7xya3zCqePMAQfBxkKFuS+WlvzoGvY9m2 7O7pbOb8q0KaqO/qSBH1E6uxq+aXwEa+YwDMDSvDsofEkAqsmsx2KtCuhI9v0kSWXHKu eOYZa90ugijbPvxO/PTWf8C4EltmNslhL7F561F1KHJzZ0ZkK0dqlwcS8hpdoP2Uw98c Rdv7OBT906R4tMx1trHpQd5YXwCaK9BNet6JdXe/31K2FI+BEEnU995cSBRB8rEPkIQ6 AxTQ==
X-Gm-Message-State APjAAAVjJk68oQGS05a5Hlfp0ownYlMDXsU0A8hoi5JzF8k6ikSuQQFa lazJvIlyzzgq0JitSBk9gfPonujF
X-Google-SMTP-Source APXvYqylFUQMugwiI65QuqWkrDOcti5JGYD70zuiTDvUNBztsZr/pYsdyotMH7HQuscYAzTAWgZ+Cg==
X-Received by 2002:adf:fc42:: with SMTP id e2mr3049224wrs.100.1571077093230; Mon, 14 Oct 2019 11:18:13 -0700 (PDT)
Openpgp preference=signencrypt
User-Agent Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version 1.0
Content-Type text/plain; charset=utf-8
Content-Language en-GB
Content-Transfer-Encoding 7bit
X-Mailing-List <debian-python@lists.debian.org> archive/latest/17441
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/b37df4a7-b4da-83de-45a1-cf0a0b19a27a@gmail.com
Approved robomod@news.nic.it
Lines 25
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Mon, 14 Oct 2019 20:18:10 +0200
X-Original-Message-ID <b37df4a7-b4da-83de-45a1-cf0a0b19a27a@gmail.com>
X-Original-References <90426bab-9b7e-468c-da1b-6815bd6e947f@debian.org> <87zhi4gfil.fsf@DigitalMercury.dynalias.net> <20191014071832.qlmr4zztkrvdmxwu@halon.org.uk>
Xref csiph.com linux.debian.maint.python:11892

Show key headers only | View raw


> As of now, calibre is not of sufficient quality to be part of a Debian release
> and until it drops all Python2 requirements, it must be considered RC buggy.

Is your quality argument based on the Calibre author's shenanigans?
https://www.reddit.com/r/linux/comments/9wodtq/calibre_wont_migrate_to_python_3_author_says_i_am/

And in particular: https://bugs.launchpad.net/calibre/+bug/1714107

One thing to consider here is the relatively large user base of Calibre that
doesn't know much or care about the Python 2 deprecation. They will simply
perceive dropping Calibre as a bad move on Debian's side and rush towards
other packages of significantly lower quality. PPAs, Snap and the like do more
harm than keeping compatibility in some way for the time being.

While I agree that Debian should not put up with stubborn developers, I also
don't agree that end users should take the fall for Debian maintainer's decisions.

Perhaps a middle ground has to be found until a viable Py3 fork of Calibre is
available, or someone steps up and writes Py3 compatibility patches without
dropping Py2 support? This here seems like a good starting to achieve what
Calibre's author wants:
https://github.com/plone/Products.CMFPlone/issues/2184#issuecomment-359445243

Though, in the long run, somebody will have to convince Kovid that writing Py3
code is worthwhile... Or take over maintenance.

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


Thread

Re: Raising severity to serious for some Python 2 leaf packages with no Python 3 support upstream Nicholas D Steeves <nsteeves@gmail.com> - 2019-10-14 05:50 +0200
  Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 09:20 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Gregor Riepl <onitake@gmail.com> - 2019-10-14 20:20 +0200
      Re: Raising severity to serious for some Python 2 leaf packages  with no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 21:30 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Gregor Riepl <onitake@gmail.com> - 2019-10-14 20:30 +0200
      Re: Raising severity to serious for some Python 2 leaf packages  with no Python 3 support upstream Neil Williams <codehelp@debian.org> - 2019-10-14 21:30 +0200
  Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@dropbear.xyz> - 2019-10-14 23:30 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@debian.org> - 2019-10-15 05:00 +0200
    Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Craig Small <csmall@dropbear.xyz> - 2019-10-15 05:20 +0200
      Re: Raising severity to serious for some Python 2 leaf packages with  no Python 3 support upstream Sandro Tosi <morph@debian.org> - 2019-10-15 19:10 +0200

csiph-web