Python 2 vs Python 3 again, and a 2.x-only dependency
What is Pypy planning to do with Python 2.x, now that many packages on Pypi are dropping Python 2.x support? EG, I believe Pypy caters to Scientific Computing, but with Numpy dropping Python 2.x support, will Pypy3 become the more relevant version of Pypy? Will Numpypy be revived? Will there be a pypypi or something similar-to-but-different-from pypi just for pypy? Will 2.x in Pypy become mostly relevant for RPython, and not most developer projects written in Python that use Pypy? I'm asking mostly because I have a large, complex dependency that isn't planning to move to Python 3.x, and I'm wondering if Pypy 2.x might be what we need to keep that code alive. But with Numpy and other dependencies dropping 2.x, that might not be enough. Thanks for Pypy, BTW. I really like it a lot.
What is the dependency? m On Mon, Jul 15, 2019 at 04:24:50PM -0700, Dan Stromberg wrote:
-- Matt Billenstein matt@vazor.com http://www.vazor.com/
Nupic: https://github.com/numenta/nupic There's a community edition that supports Python 3.x, but its license may prove unsuitable to what we're doing. On 7/15/19 4:57 PM, Matt Billenstein wrote:
The plea for migration probably won’t be technically-based; plenty of shops maintain special-case installations detached from the rest of the world. The issue resides in general skills and available volunteers - the more specialized the requirements, the less sustainable. Being 2-based requires expertise with 2 - there’s no other way about it. As 2 fades, that expertise will fade as well. I doubt there’s an immediate need to move to 3 for RPython right now. There may be a need in the later future (years?). Or not. Predicting the future is quite difficult. Ben
On Tue, Jul 16, 2019 at 1:35 AM William ML Leslie < william.leslie.ttg@gmail.com> wrote:
Expertise is one thing. Another: it's getting harder, as time goes by, to find 2.x versions of sometimes-important dependencies. numpy, pandas, matplotlib, pip itself - they're all dropping 2.x support.
Hi Ryan RPython has no plans to move to python3. There are no dependencies that we can't vendor that will become a problem. We expect Python2 to be available (and pypy stepping in if necessary) for a long time in the future. The reason is very prosaic - it's a lot of work for absolutely no reward. It has nothing to do with a vision and opinions etc. The only win we would have is that we can then drop support for having Python 2 interpreter. But we're not going to do that! Vast majority of PyPy users use Python 2 and it might stay that way for quite some time. Best, Maciej Fijalkowski On Wed, Jul 17, 2019 at 5:09 AM Ryan Gonzalez <rymg19@gmail.com> wrote:
What is the dependency? m On Mon, Jul 15, 2019 at 04:24:50PM -0700, Dan Stromberg wrote:
-- Matt Billenstein matt@vazor.com http://www.vazor.com/
Nupic: https://github.com/numenta/nupic There's a community edition that supports Python 3.x, but its license may prove unsuitable to what we're doing. On 7/15/19 4:57 PM, Matt Billenstein wrote:
The plea for migration probably won’t be technically-based; plenty of shops maintain special-case installations detached from the rest of the world. The issue resides in general skills and available volunteers - the more specialized the requirements, the less sustainable. Being 2-based requires expertise with 2 - there’s no other way about it. As 2 fades, that expertise will fade as well. I doubt there’s an immediate need to move to 3 for RPython right now. There may be a need in the later future (years?). Or not. Predicting the future is quite difficult. Ben
On Tue, Jul 16, 2019 at 1:35 AM William ML Leslie < william.leslie.ttg@gmail.com> wrote:
Expertise is one thing. Another: it's getting harder, as time goes by, to find 2.x versions of sometimes-important dependencies. numpy, pandas, matplotlib, pip itself - they're all dropping 2.x support.
Hi Ryan RPython has no plans to move to python3. There are no dependencies that we can't vendor that will become a problem. We expect Python2 to be available (and pypy stepping in if necessary) for a long time in the future. The reason is very prosaic - it's a lot of work for absolutely no reward. It has nothing to do with a vision and opinions etc. The only win we would have is that we can then drop support for having Python 2 interpreter. But we're not going to do that! Vast majority of PyPy users use Python 2 and it might stay that way for quite some time. Best, Maciej Fijalkowski On Wed, Jul 17, 2019 at 5:09 AM Ryan Gonzalez <rymg19@gmail.com> wrote:
participants (8)
-
Ben Jolitz -
Dan Stromberg -
Dan Stromberg -
Maciej Fijalkowski -
Matt Billenstein -
Ryan Gonzalez -
William ML Leslie -
Yury V. Zaytsev