[pypy-dev] Question on the future of RPython

Amaury Forgeot d'Arc amauryfa at gmail.com
Fri Sep 3 20:16:11 CEST 2010

2010/9/3 Saravanan Shanmugham <sarvi at yahoo.com>
> I have heard repeatedly in this alias that PyPy's RPython is very difficult to
> use.
> I have also heard here and elsewhere that Shedskin fast and is great for what it
> does i.e. translate its version of Restricted Python to C++.
> Which then begs the question, would it make sense for PyPy to adopt Shedskin to
> compile its PyPy RPython code into C++/binary.

But PyPy does not translate RPython code to C++.
Or before doing so, it performs transformations to the code that
require the analysis
of the program as a whole and that a C++ compiler cannot do, like the choice
of a garbage collector, the stackless mode, and most of all the
generation of a tracing JIT.

It also operates on the bytecode, which offers interesting
metaprogramming techniques
that are used throughout the code (similar to C++ templates, for example,
except that it's written in Python :-) )

Shedskin on the other hand performs a more direct translation of
Python code (it uses the ast)

Both projects don't have the same goals.

Amaury Forgeot d'Arc

More information about the Pypy-dev mailing list