Thank you so much for taking the time to comment on this. I have very little vested in (any) python (distribution) - but would love to see "real" python3-support in pypy.
As the sibling comment mentions: Maybe now is the time to try for another funding run for py3 support? A lot of frameworks and libraries have been ported, and a lot of new code is being written for py3. Perhaps there'd also be real interest from people that now look at pypy as "just" "performance enhancement for legacy py2" to see py3 on the pypy platform?
In my personal opinion the speed gains of pypy aren't really all that interesting (other than perhaps, in the sense that it enables more code in python rather than c etc). But rpython+pypy as a framework for language development in general, and as a host for python in particular (along with the work on cffi) are really great aspects of pypy.
And while anyone can get rolling with rpython and implement their own toy prolog/brainfuck/whatever -- other benefits from running python on pypy will remain out of reach for those that for various reasons are targeting py3.
Then, maybe we could do another funding run to get mercurial ported to py3, later ;-)
At any rate, I love the work that is being done on pypy, and I certainly think it doesn't make sense to devout resources to py3 "just because new"; I believe free software development works best when driven by stakeholders. But I think the fact that "pypy doesn't really work for py3 also drives some people away from pypy that might otherwise contribute in various ways to help push py3 support further.
As the sibling comment mentions: Maybe now is the time to try for another funding run for py3 support? A lot of frameworks and libraries have been ported, and a lot of new code is being written for py3. Perhaps there'd also be real interest from people that now look at pypy as "just" "performance enhancement for legacy py2" to see py3 on the pypy platform?
In my personal opinion the speed gains of pypy aren't really all that interesting (other than perhaps, in the sense that it enables more code in python rather than c etc). But rpython+pypy as a framework for language development in general, and as a host for python in particular (along with the work on cffi) are really great aspects of pypy.
And while anyone can get rolling with rpython and implement their own toy prolog/brainfuck/whatever -- other benefits from running python on pypy will remain out of reach for those that for various reasons are targeting py3.
Then, maybe we could do another funding run to get mercurial ported to py3, later ;-)
At any rate, I love the work that is being done on pypy, and I certainly think it doesn't make sense to devout resources to py3 "just because new"; I believe free software development works best when driven by stakeholders. But I think the fact that "pypy doesn't really work for py3 also drives some people away from pypy that might otherwise contribute in various ways to help push py3 support further.