4 ms·

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 divisio

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

kzrdude 6y ago
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.
- neolog 6y ago
  The main reason to move to py3 is the libraries, but they're not using any libraries.
  - kzrdude 6y ago
    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.
    - deleted 6y ago
      [deleted]
- progval 6y ago
  > Why do they hang on to Python2.7? https://doc.pypy.org/en/latest/faq.html#how-long-will-pypy-support-python2 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.
  - kzrdude 6y ago
    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.
  - d0mine 6y ago
    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.
raverbashing 6y ago
Cool now do UnicodeDecodeError :)
- baq 6y ago
  And print a traceback of a re-raised exception :)

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

kzrdude 6y ago

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.

neolog 6y ago
The main reason to move to py3 is the libraries, but they're not using any libraries.
- kzrdude 6y ago
  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.
  - deleted 6y ago
    [deleted]
progval 6y ago
> Why do they hang on to Python2.7? https://doc.pypy.org/en/latest/faq.html#how-long-will-pypy-support-python2 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.
- kzrdude 6y ago
  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.
- d0mine 6y ago
  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.

raverbashing 6y ago

Cool now do UnicodeDecodeError :)

baq 6y ago
And print a traceback of a re-raised exception :)