This gives us an opportunity to define a more general purpose definition of RPython. Based on previous threads, RPython as currently defined in PyPy is up for general use. And the team seems to have no interest in exploring this RPython for general use. And to be honest I can see some extent why. Keeps it simple and domain specific for the purpose of language definition which is PyPy's goals. So my intent is to instead go for more general purpose RPython, by starting with Shedskin's definition of Restricted Python, which is pretty close to PyPy's RPython Refer to Hart's comparison here. http://groups.google.com/group/shedskin-discuss/browse_thread/thread/a8b473f... Why port shedskin onto PyPy. 1. See if PyPy as a language definition framework can be used generate compilers and not just Interpreters. 2. Leverage the C++ code under shedskin/lib to quickly get to that goal. 3. I am thinking bringing them together will bring more interest and momentum to both PyPy but more importantly a general purpose Restricted Python Compiler. Sarvi ----- Original Message ----

From: Benjamin Peterson <benjamin@python.org> To: PyPy Dev <pypy-dev@codespeak.net> Sent: Tue, September 14, 2010 3:19:36 PM Subject: [pypy-dev] Fwd: PyPy to generate C/C++ code

---------- Forwarded message ---------- From: Benjamin Peterson <benjamin@python.org> Date: 2010/9/14 Subject: Re: [pypy-dev] PyPy to generate C/C++ code To: Saravanan Shanmugham <sarvi@yahoo.com>

2010/9/14 Saravanan Shanmugham <sarvi@yahoo.com>:

...

I don't expect this python compiler to be for full python but just a Restricted statically typed subset of python as defined by Shedskin.

So how is that any different than the existing RPython?

-- Regards, Benjamin

-- Regards, Benjamin _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev