[pypy-commit] pypy default: Merged in techtonik/pypy-1/techtonik/introductionrst-simplify-explanation-abo-1460879168046 (pull request #429)
arigo
pypy.commits at gmail.com
Fri Apr 22 06:34:42 EDT 2016
Author: Armin Rigo <armin.rigo at gmail.com>
Branch:
Changeset: r83825:63c7bb7b783d
Date: 2016-04-22 12:33 +0200
http://bitbucket.org/pypy/pypy/changeset/63c7bb7b783d/
Log: Merged in techtonik/pypy-1/techtonik/introductionrst-simplify-
explanation-abo-1460879168046 (pull request #429)
introduction.rst simplify explanation about PyPy
diff --git a/pypy/doc/introduction.rst b/pypy/doc/introduction.rst
--- a/pypy/doc/introduction.rst
+++ b/pypy/doc/introduction.rst
@@ -1,16 +1,22 @@
What is PyPy?
=============
-In common parlance, PyPy has been used to mean two things. The first is the
-:ref:`RPython translation toolchain <rpython:index>`, which is a framework for generating
-dynamic programming language implementations. And the second is one
-particular implementation that is so generated --
-an implementation of the Python_ programming language written in
-Python itself. It is designed to be flexible and easy to experiment with.
+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_ 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.
-This double usage has proven to be confusing, and we are trying to move
-away from using the word PyPy to mean both things. From now on we will
-try to use PyPy to only mean the Python implementation, and say the
+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 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
More information about the pypy-commit
mailing list