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

Future of PyPy (not PyPy3) in Debian

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Sandro Tosi <morph@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Future of PyPy (not PyPy3) in Debian
Date	Fri, 05 Jun 2020 02:10:02 +0200
Message-ID	<Ae85Q-4JN-9@gated-at.bofh.it> (permalink)
X-Original-To	debian-python <debian-python@lists.debian.org>, Stefano Rivera <stefanor@debian.org>
X-Mailbox-Line	From debian-python-request@lists.debian.org Fri Jun 5 00:01:13 2020
Old-Return-Path	<sandro.tosi@gmail.com>
X-Amavis-Spam-Status	No, score=-6.5 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5.5
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=UiHdHHuzuVI701Ua5YAvLM7aiMYzUmMCQCH1onw+OLM=; b=GP5J7D9cG+2d6REXneCt/k01DfAcbJegUX4M874h/2JGKH+OeAGGHKWGzvcz9c+1Ox UyKInSWD6+d/YRdz4d+5sQxZb3PklJzDxjUdCmNmWmXfwmVedDrDK8PRXgUUkQ7eR++X SMN8JBkznSZC551Y2XfrIVUwFEpccMgVcO5iVaKPVoBKXyXvlbYFFElkD6SxhmhG7BAO 99eFEJ95EbBNQ6GfxOkZ4eR8txER3A3Qd18PALfHao3fJ6ywTjVuNy+NVe+WUbWUHJDS J2sGKUvLyLkkd2EfPlpsETcLk5/qK2Sp4+5vctYPPeqRVzT2UhlSIXu2wyc/eSh/fjjq SlkQ==
X-Gm-Message-State	AOAM530x6J3hZeAjDvp/KDjEQipF9u3LNE/B//8YA0VIP5+JlF6T+6kd oWhKiyUHBnvQ5wM0/UMgKCbCA/nsOLm7OEky6P8OqRqV
X-Google-SMTP-Source	ABdhPJzBizb5l9RmlkJRrTJC1KXJFOVqXMQPXZw/7xOP+CJxVwVoO+GTBAnvG9kl9M6NkMy5zXXZCDBExGl+C7Q5v4w=
X-Received	by 2002:a37:9781:: with SMTP id z123mr7206567qkd.256.1591315256266; Thu, 04 Jun 2020 17:00:56 -0700 (PDT)
MIME-Version	1.0
Content-Type	text/plain; charset="UTF-8"
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/18332
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/CAB4XWXztp7Z6jLBN4Mj4c6FjBKF0N3vi=0uCuJxd5M+ZDf82XA@mail.gmail.com
Approved	robomod@news.nic.it
Lines	21
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 4 Jun 2020 20:00:30 -0400
X-Original-Message-ID	<CAB4XWXztp7Z6jLBN4Mj4c6FjBKF0N3vi=0uCuJxd5M+ZDf82XA@mail.gmail.com>
Xref	csiph.com linux.debian.maint.python:12627

Show key headers only | View raw

Hello all,
it looks like i started a process that would require the removal of
several PyPy (as in pypy-* depending on the `pypy` package) packages
from the archive.

I'm now wondering: what should we do with the entire pypy ecosystem?
should we treat pypy-* packages like python-* ones and remove then as
part of py2removal? do we need/want to track this effort with the same
usertag? is there a (even if only hypothetical for now) programmed
transition from pypy- to pypy3-?

PS: if i made mistakes, just call me out, and i'll do my best to fix
them or revert them; i have no problem in being told i did something
wrong (let's keep the discussion in this thread on topic, so pypy etc)

Cheers,
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

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

Thread

Future of PyPy (not PyPy3) in Debian Sandro Tosi <morph@debian.org> - 2020-06-05 02:10 +0200
  Re: Future of PyPy (not PyPy3) in Debian stefanor@debian.org - 2020-06-05 07:40 +0200

csiph-web