Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12629
| Path | csiph.com!2.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | stefanor@debian.org |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Future of PyPy (not PyPy3) in Debian |
| Date | Fri, 05 Jun 2020 07:40:02 +0200 |
| Message-ID | <Aedfc-7Rc-9@gated-at.bofh.it> (permalink) |
| References | <Ae85Q-4JN-9@gated-at.bofh.it> |
| X-Original-To | Sandro Tosi <morph@debian.org> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Fri Jun 5 05:38:52 2020 |
| Old-Return-Path | <stefano@rivera.za.net> |
| X-Amavis-Spam-Status | No, score=-6.851 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate:hard: -4.6 |
| X-Greylist | delayed 616 seconds by postgrey-1.36 at bendel; Fri, 05 Jun 2020 05:38:39 UTC |
| Dkim-Signature | v=1; a=ed25519-sha256; c=relaxed/simple; d=debian.org; i=@debian.org; q=dns/txt; s=satie-ed25519.stefanor.user; t=1591334878; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to : from; bh=rqqpKHyd77ooqsDrR2kv8IzHFTvb6a6SmHFaETMigWM=; b=ztdQvrUeahMh1EA8s2oQ4HkmcSvyhkNznuI0VoORfUSzJEDVObmEOpWFbJNux7rMkMayH GvtOZqsoCXsXdbVAA== |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/simple; d=debian.org; i=@debian.org; q=dns/txt; s=satie-rsa.stefanor.user; t=1591334878; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to : from; bh=rqqpKHyd77ooqsDrR2kv8IzHFTvb6a6SmHFaETMigWM=; b=BZ6tFmfZrYv4lBwRsIBjs+Pidtvs9cmJzAkcNtsXvFSqLl9z+UKcuawT5R1MsJGjFP9En PtHThE09H3ZQKhQHK3bjgm3FyabtmBKRZmK5NMEhpzKC4s87iJSV8Xt7yBS0yRKV90t5F/l Z+jPWqTz50fQ5T9Ct4GQGm/a2LvIDgXE2GSkq1vpvX3WPYeSshETacGZ7UOqPA4ejjrWoZ5 B/f5fHi0IjwGjcqe7BoEK45d2uZRlBY1OWduHMMfLxtOSbyu89jRmU3kteSB1Sn1MWT4Uik VlqqOtJtj3mui++mf+4fUlJMvK1SvWCDFxGEyjd8bcuYBevb/lA9NEOeMTBA== |
| Mail-Followup-To | Sandro Tosi <morph@debian.org>, debian-python <debian-python@lists.debian.org> |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=utf-8 |
| Content-Disposition | inline |
| X-Gpg-Public-Key | http://www.rivera.za.net/stefano.gpg |
| User-Agent | NeoMutt/20180716 |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/18335 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/20200605052758.7lhabccc3s7qmfd6@satie.tumbleweed.org.za |
| Approved | robomod@news.nic.it |
| Lines | 47 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Cc | debian-python <debian-python@lists.debian.org> |
| X-Original-Date | Fri, 5 Jun 2020 05:27:58 +0000 |
| X-Original-Message-ID | <20200605052758.7lhabccc3s7qmfd6@satie.tumbleweed.org.za> |
| X-Original-References | <CAB4XWXztp7Z6jLBN4Mj4c6FjBKF0N3vi=0uCuJxd5M+ZDf82XA@mail.gmail.com> |
| Xref | csiph.com linux.debian.maint.python:12629 |
Show key headers only | View raw
Hi Sandro (2020.06.05_00:00:30_+0000) > I'm now wondering: what should we do with the entire pypy ecosystem? Big picture: Upstream is continuing to support pypy (2.7) for the foreseeable future. I don't know what that will look like for stdlib support. But they need a 2.7 interpreter for the rpython toolchain, so they're forced to support it. They're starting to talk about porting rpython to python 3. But that's probably a few years away, at least. I need a 2.7 to build pypy3 (rpython). That could be cpython or pypy. Currently both, pypy for the archs it has JIT support for, cpython for the rest and bootstrapping new archs. My ideal would be to continue like that. As long as pypy is in the archive, I'd like it to be supported by virtualenv, so that it's also useful to users. > should we treat pypy-* packages like python-* ones and remove then as > part of py2removal? Generally speaking those pypy- libraries aren't needed. It looks like we have only one app in the archive depending on them. If upstreams drop Python 2.7 compatibility, these will have to go, anyway. > do we need/want to track this effort with the same usertag? You can probably get away with the same usertag. There are far fewer of them. > is there a (even if only hypothetical for now) programmed transition > from pypy- to pypy3-? pypy3 uses /usr/lib/python3/dist-packages/ so there aren't pypy3- packages (except for ones built by src:pypy3), just python3- packages. That works well enough for pure Python, but there's no way to express dependencies for C extensions, usefully. I guess we may end up with some pypy3- packages for that (although that won't completely solve the problem). Not a problem we've faced, yet. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll 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