Bug#825970: pypy: Please package pypy3 as well now
Hi Jeroen (2018.07.26_12:46:39_+0100) > > Python2 is dying. Is there any reason so that pypy3 shouldn't be > > compiled and uploaded? If you lack time and need help, please just ask. It's mostly been time, yes. > I'd also like to see pypy3 packaged. Is there already any work done on > packaging pypy3? If not then we should probably start with creating a > pypy3 source package based on the pypy2 packaging. I've had something mostly ready to go for a year or so :/ https://salsa.debian.org/debian/pypy3 amd64 builds: https://people.debian.org/~stefanor/pypy3/ (which I'll update with 6.0.0, shortly) The remaining issue that I know of, is figuring out a plan for byte-compilation. I'll bring it up on the debian-python list... SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#825970: pypy: Please package pypy3 as well now
On Wed, 11 Jul 2018 11:38:31 +0200, Lumin wrote: > Python2 is dying. Is there any reason so that pypy3 shouldn't be > compiled and uploaded? If you lack time and need help, please just ask. I'd also like to see pypy3 packaged. Is there already any work done on packaging pypy3? If not then we should probably start with creating a pypy3 source package based on the pypy2 packaging.
Bug#825970: pypy: Please package pypy3 as well now
Hi Stefano, Python2 is dying. Is there any reason so that pypy3 shouldn't be compiled and uploaded? If you lack time and need help, please just ask.
Bug#825970: pypy: Please package pypy3 as well now
Package: pypy Version: 6.0.0+dfsg-1 Followup-For: Bug #825970 pypy 6 is officially a dual 2.7/3.5 release. It would be very nice to have a pypy3 package. I have to keep a custom build, since I no longer develop on 2.7 since quite some time now. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pypy depends on: ii dpkg 1.19.0.5.0~reproducible1 ii libbz2-1.01.0.6-8.1 ii libc6 2.27-3 ii libexpat1 2.2.5-3 ii libffi6 3.2.1-8 ii libgcc1 1:8-20180425-1 ii libgdbm5 1.14.1-6 ii libncurses6 6.1+20180210-2 ii libsqlite3-0 3.23.1-1 ii libssl1.1 1.1.0h-2 ii libtinfo6 6.1+20180210-2 ii pypy-lib 6.0.0+dfsg-1 ii zlib1g1:1.2.11.dfsg-1 pypy recommends no packages. Versions of packages pypy suggests: ii pypy-doc 6.0.0+dfsg-1 pn pypy-tk
Bug#825970: pypy: Please package pypy3 as well now
Package: pypy Version: 5.6.0+dfsg-4 Followup-For: Bug #825970 Any progress / requests for help / things we can do? -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (700, 'stable'), (650, 'oldstable'), (600, 'unstable'), (550, 'experimental'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pypy depends on: ii dpkg 1.18.24 ii libbz2-1.01.0.6-8.1 ii libc6 2.24-11+deb9u1 ii libexpat1 2.2.0-2+deb9u1 ii libffi6 3.2.1-6 ii libgdbm3 1.8.3-14 ii libncurses5 6.0+20161126-1 ii libsqlite3-0 3.16.2-5 ii libssl1.1 1.1.0f-3 ii libtinfo5 6.0+20161126-1 ii pypy-lib 5.6.0+dfsg-4 ii zlib1g1:1.2.8.dfsg-5 pypy recommends no packages. Versions of packages pypy suggests: pn pypy-doc pn pypy-tk -- no debconf information
Bug#825970: pypy: Please package pypy3 as well now
Package: pypy Version: 5.1.2+dfsg-1 Severity: wishlist Dear Maintainer, Yesterday, the first alpha of PyPy3 v5.2 (supporting 3.3) was released. While the actual release is still some time off, now would be a good time to start getting the infrastructure ready, either in experimental or in unstable-with-a-blocking-bug (the latter might be more friendly for packages that wish to release versions for both cpython and pypy). Note that upstream pypy3 is released as a separate product (and thus likely source package) despite being in the same repository. PyPy3 v5.2 is now much more mature than the previous v2.4 release (which was released shortly after the same-numbered PyPy2 release - the whatsnew and release files for PyPy2 are much more thorough and generally still applicable), and I've been using snapshots happily for a while. -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pypy depends on: ii dpkg 1.18.7 ii libbz2-1.01.0.6-8 ii libc6 2.22-9 ii libexpat1 2.1.1-2 ii libffi6 3.2.1-4 ii libgdbm3 1.8.3-13.1 ii libncurses5 6.0+20160319-1 ii libsqlite3-0 3.13.0-1 ii libssl1.0.2 1.0.2h-1 ii libtinfo5 6.0+20160319-1 ii pypy-lib 5.1.2+dfsg-1 ii zlib1g1:1.2.8.dfsg-2+b1 pypy recommends no packages. Versions of packages pypy suggests: ii pypy-doc 5.1.2+dfsg-1 pn pypy-tk -- no debconf information
