Steven D'Aprano, 16.02.2013 07:13: > On 16/02/13 16:41, Stefan Behnel wrote: > >>> PyPy is indeed a work in progress in this area, but that doesn't >>> necessarily preclude it from being included. >> >> That may be a matter of POV, but as long as PyPy fails to integrate (and >> you just called that "not a main focus"), I find it hard to defend its >> relevance. > > Stefan, you're talking about a website which lists projects such as a Forth- > like language in Python, a bytecode transformer, a project "Peregine-Falcon" > which appears to be a one-man experimental implementation of Python in C++, > ByteRun, a "pure-Python implementation of a Python bytecode execution > virtual machine", and SPARK, which has been stuck in version 0.7 pre-alpha > for years. I am astonished that you think PyPy is too immature or niche for > this list. > > http://compilers.pydata.org/
Hmm, I don't have the feeling that this discussion is leading anywhere (especially not on this list). After all, it's quite possible to fire up a PyPy runtime from a CPython runtime and have them talk to each other, letting each one do what it's good at. That doesn't make PyPy a "compiler for CPython", but at least it means that it doesn't fail completely to integrate with the rest of the world. There are arguments for both sides, which means in dubio pro reo, I guess. Stefan _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
