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
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
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.
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
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')
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
6 matches
Mail list logo
