News for hackers. Stuff that matters.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by benatkin on Sunday September 27, 2020 @02:44AM (#24604717)
Long live Python2 :)

    docker run pypy:2.7-7.3.2 python -c "print 'no quotes, integer division %s / %s => %s' % (5, 3, 5 / 3)"
    no quotes, integer division 5 / 3 => 1
Edit: i mean no parenthesis
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by kzrdude on Sunday September 27, 2020 @03:15AM (#24604862)
Why do they hang on to Python2.7? I suppose it doesn't have so much maintenance cost for them.

I have to say that their official benchmarks point out a performance comparison to python 2.7, and at this time that sounds irrelevant - comparison to Python 3 would be relevant.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by progval on Sunday September 27, 2020 @05:00AM (#24605236)
> Why do they hang on to Python2.7?

https://doc.pypy.org/en/latest/faq.html#how-long-will-pypy-s...

PyPy is written in RPython, which is a subset of Python 2 without most of the dynamic features, so it can be compiled. Moving it to a subset of Python 3 would be a major effort, as they would have to rewrite both the PyPy code and the RPython compiler.

And RPython, being a subset of Python, can also be interpreted, so they probably want to keep the Python 2 interpreter so they can interpret it.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by d0mine on Sunday September 27, 2020 @07:08AM (#24605776)
Given how limited RPython is, are you sure RPython is not Python 2/3 compatible as is? What Python 2 only features it uses?

The faq that you've linked says that RPython will continue to run on Python 2 as long as Pypy exists, it says nothing about running RPython on Python 3 interpreter.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by kzrdude on Sunday September 27, 2020 @05:40AM (#24605429)
Thanks, that's understandable.

I think that they should switch to displaying and talking about Py 3 comparison benchmarks to give the impression that they are a non-legacy project.

Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by neolog on Sunday September 27, 2020 @03:29AM (#24604911)
The main reason to move to py3 is the libraries, but they're not using any libraries.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by kzrdude on Sunday September 27, 2020 @04:36AM (#24605147)
It must rather be about what their users need - their users use libraries for sure. But maybe their users are still on Py 2.7.
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by raverbashing on Sunday September 27, 2020 @03:35AM (#24604935)
Cool now do UnicodeDecodeError :)
Re:PyPy 7.3.2 triple release: Python 2.7, 3.6, and 3.7 by baq on Sunday September 27, 2020 @03:49AM (#24604992)
And print a traceback of a re-raised exception :)