On Mon, Dec 24, 2012 at 11:24 AM, William ML Leslie <william.leslie.ttg@gmail.com> wrote:

Ugh, hit the wrong reply button.

On 24 December 2012 19:24, William ML Leslie

<william.leslie.ttg@gmail.com> wrote:
> On 24 December 2012 19:03, anatoly techtonik <techtonik@gmail.com> wrote:
>> Hi,
>>
>> The PyPy description in getting started is still too scientific. I attach a
>> patch with accessibility fix. =) But it is still not completely clear if
>> PyPy's Python implementation is written in Python or in RPython?
>
> They aren't mutually exclusive; all rpython is python.

But it is still confusing, because the RPython doesn't include generators, which means Python implementation is still written in subset of Python and not using the real full fat Python.

>> '''And the second is one particular implementation that is so generated – an
>> implementation of the Python programming language written in Python
>> itself.'''
>
> Maybe we could be even clearer - in my mind, implementations aren't
> generated, they do have to be written (:

I looks like the documentation is missing one more important aspect - RPython toolchain can be used to compile standalone programs written in RPython (which is why I've finally got to it at the moment).

>> If Python implementation is written in Python, and not in RPython then there
>> is the missing link between the framework and implementation, which is
>> confusing.
>>
>> http://doc.pypy.org/en/latest/getting-started.html#what-is-pypy