Author: anatoly techtonik <techto...@gmail.com> Branch: techtonik/introductionrst-simplify-explanation-abo-1460879168046 Changeset: r83824:c54661e15b83 Date: 2016-04-22 10:10 +0000 http://bitbucket.org/pypy/pypy/changeset/c54661e15b83/
Log: introduction.rst add comments be Armin Rigo diff --git a/pypy/doc/introduction.rst b/pypy/doc/introduction.rst --- a/pypy/doc/introduction.rst +++ b/pypy/doc/introduction.rst @@ -4,14 +4,19 @@ Historically, PyPy has been used to mean two things. The first is the :ref:`RPython translation toolchain <rpython:index>` for generating interpreters for dynamic programming languages. And the second is one -particular implementation of Python_ generated with it. Because RPython +particular implementation of Python_ produced with it. Because RPython uses the same syntax as Python, this generated version became known as Python interpreter written in Python. It is designed to be flexible and easy to experiment with. +To make it more clear, we start with source code written in RPython, +apply the RPython translation toolchain, and end up with PyPy as a +binary executable. This executable is the Python interpreter. + Double usage has proven to be confusing, so we've moved away from using -the word PyPy to mean both things. Now we use word PyPy to refer to -the Python implementation, and explicitly mention +the word PyPy to mean both toolchain and generated interpreter. Now we +use word PyPy to refer to the Python implementation, and explicitly +mention :ref:`RPython translation toolchain <rpython:index>` when we mean the framework. Some older documents, presentations, papers and videos will still have the old _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit
