Luis M. González wrote:
> Thanks!
> I think I completely understand the whole thing now :-)

If only we could say the same :-)

> Anyway, I guess it's just a matter of time untill we can use this
> translation tool to translate other programs, provided they are written
> in restricted python, right?

Yes. This is even possible right now, with one caveat: Basically it is 
not so hard to write a new program in RPython. RPython is still kind of 
nice, it is testable on CPython so this is not such a bad task. There 
are problems with that, though: You don't have most of the stdlib in 
RPython (mostly only a few functions from os, sys, math work). The other 
problem is that it is quite hard to convert /existing/ programs to 
RPython because they will most probably not adhere to the staticness 
conditions. And it is surprisingly hard to convert an existing program 
to RPython.

> So we will have two choices:
> 1) running normal python programs on Pypy.
> 2) translating rpython programs to C and compiling them to stand-alone
> executables.
> 
> Is that correct?

Indeed. Another possibility is to write a PyPy extension module in 
RPython, have that translated to C and then use this in your pure python 
code. Actually, one of our current rather wild ideas (which might not be 
followed) is to be able to even use RPython to write extension modules 
for CPython.

Cheers,

Carl Friedrich Bolz

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to