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

Re: Future of PyPy (not PyPy3) in Debian

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Scott Kitterman <debian@kitterman.com>
Newsgroups	linux.debian.maint.python
Subject	Re: Future of PyPy (not PyPy3) in Debian
Date	Fri, 05 Jun 2020 02:10:02 +0200
Message-ID	<Ae85Q-4JN-7@gated-at.bofh.it> (permalink)
References	<Ae85Q-4JN-9@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Fri Jun 5 00:05:38 2020
Old-Return-Path	<debian@kitterman.com>
X-Amavis-Spam-Status	No, score=-12.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, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5.5
Dkim-Signature	v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1591315524; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type : from; bh=xvYzvbnZM1ASbR3TFtCAuX9RVHRAAG1vsBxGYpeGg6g=; b=MXQFo4XbvhjOdSEFDMwOQgVoaFA2IoqNGrI0OZ9oeAjHngkGotWn5XP4IuFJlyD+CFV1C Ob8Hnpd7HloviUNBw==
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1591315524; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type : from; bh=xvYzvbnZM1ASbR3TFtCAuX9RVHRAAG1vsBxGYpeGg6g=; b=O0lV8tC40PSvdK2UTuHFiw5+1bFYsBcG0GwKeTY/ykselq9rj5qdooODliMV9bv5HooPZ zkt7YUN4gEhFTk6r8TDnGe35frGJQY6FVaYBjOukAQ4AvlNHNaRXzSeWbpB17iSGH6H9Ume 0HMYB48gD3wvpQpGVYcp/Gp2fdMF+GfQCnXSQCx+Cligv0yemisTx0O0r1nN1/hLMuFemNH 56cYZdgDT3aR2zb0cvI9w1fUx9RplK+PGCCjKzNif3TLBmaQ1M0P2IEJwIyoBz28/c2cmJa 5KCaPh5GKCDEaINJdS3VhxkZ5lpSaQSSW+4WQq1oMdMeyhBF9DpddcgPiOSg==
MIME-Version	1.0
Content-Type	multipart/signed; boundary="nextPart3284975.ejoLCngriW"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/18333
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/5157358.mTLUhKFVQY@sk-desktop
Approved	robomod@news.nic.it
Lines	57
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 04 Jun 2020 20:05:24 -0400
X-Original-Message-ID	<5157358.mTLUhKFVQY@sk-desktop>
X-Original-References	<CAB4XWXztp7Z6jLBN4Mj4c6FjBKF0N3vi=0uCuJxd5M+ZDf82XA@mail.gmail.com>
Xref	csiph.com linux.debian.maint.python:12626

Show key headers only | View raw

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

On Thursday, June 4, 2020 8:00:30 PM EDT Sandro Tosi wrote:
> 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)

My understanding is that unlike python2.7, pypy is not going away.  If nothing 
else it's needed to build pypy3.

Tumbleweed and I recently did some integration work to make sure pip and 
virtualenv for Bullseye will support pypy and pypy3.  In fact, a pypy 
virtualenv may be a decent solution for people with python2 code that isn't 
ported to python3 yet.  I'd hate to mess that up.

I think we need to keep some of pypy.  The question is how much.

Since Tumbleweed is the one most familiar with the environment, I defer to him 
on the specifics about what we need to keep.

Scott K

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

Thread

Re: Future of PyPy (not PyPy3) in Debian Scott Kitterman <debian@kitterman.com> - 2020-06-05 02:10 +0200

csiph-web