[pypy-commit] pypy default: update docs
Author: David Schneider david.schnei...@picle.org Branch: Changeset: r65553:f38b470ae432 Date: 2013-07-23 13:35 +0200 http://bitbucket.org/pypy/pypy/changeset/f38b470ae432/ Log:update docs diff --git a/pypy/doc/how-to-release.rst b/pypy/doc/how-to-release.rst --- a/pypy/doc/how-to-release.rst +++ b/pypy/doc/how-to-release.rst @@ -30,7 +30,7 @@ * update README * change the tracker to have a new release tag to file bugs against * go to pypy/tool/release and run: - force-builds.py /release/release branch + force-builds.py release branch * wait for builds to complete, make sure there are no failures * upload binaries to https://bitbucket.org/pypy/pypy/downloads ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs
Author: Maciej Fijalkowski fij...@gmail.com Branch: Changeset: r63947:13062596965a Date: 2013-05-09 19:41 +0200 http://bitbucket.org/pypy/pypy/changeset/13062596965a/ Log:update docs diff --git a/pypy/doc/conf.py b/pypy/doc/conf.py --- a/pypy/doc/conf.py +++ b/pypy/doc/conf.py @@ -47,7 +47,7 @@ # The short X.Y version. version = '2.0' # The full version, including alpha/beta/rc tags. -release = '2.0-beta1' +release = '2.0.0' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/pypy/doc/getting-started-python.rst b/pypy/doc/getting-started-python.rst --- a/pypy/doc/getting-started-python.rst +++ b/pypy/doc/getting-started-python.rst @@ -105,7 +105,7 @@ $ ./pypy-c Python 2.7.3 (7e4f0faa3d51, Nov 22 2012, 10:35:18) -[PyPy 2.0.0-beta1 with GCC 4.7.1] on linux2 +[PyPy 2.0.0 with GCC 4.7.1] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``RPython magically makes you rich and famous (says so on the tin)'' @@ -235,7 +235,7 @@ the ``bin/pypy`` executable. To install PyPy system wide on unix-like systems, it is recommended to put the -whole hierarchy alone (e.g. in ``/opt/pypy2.0-beta1``) and put a symlink to the +whole hierarchy alone (e.g. in ``/opt/pypy2.0``) and put a symlink to the ``pypy`` executable into ``/usr/bin`` or ``/usr/local/bin`` If the executable fails to find suitable libraries, it will report diff --git a/pypy/doc/getting-started.rst b/pypy/doc/getting-started.rst --- a/pypy/doc/getting-started.rst +++ b/pypy/doc/getting-started.rst @@ -53,10 +53,10 @@ PyPy is ready to be executed as soon as you unpack the tarball or the zip file, with no need to install it in any specific location:: -$ tar xf pypy-2.0-beta1-linux.tar.bz2 -$ ./pypy-2.0-beta1/bin/pypy +$ tar xf pypy-2.0.tar.bz2 +$ ./pypy-2.0/bin/pypy Python 2.7.3 (7e4f0faa3d51, Nov 22 2012, 10:35:18) -[PyPy 2.0.0-beta1 with GCC 4.7.1] on linux2 +[PyPy 2.0.0 with GCC 4.7.1] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``PyPy is an exciting technology that lets you to write fast, portable, multi-platform interpreters with less @@ -75,14 +75,14 @@ $ curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py -$ ./pypy-2.0-beta1/bin/pypy distribute_setup.py +$ ./pypy-2.0/bin/pypy distribute_setup.py -$ ./pypy-2.0-beta1/bin/pypy get-pip.py +$ ./pypy-2.0/bin/pypy get-pip.py -$ ./pypy-2.0-beta1/bin/pip install pygments # for example +$ ./pypy-2.0/bin/pip install pygments # for example -3rd party libraries will be installed in ``pypy-2.0-beta1/site-packages``, and -the scripts in ``pypy-2.0-beta1/bin``. +3rd party libraries will be installed in ``pypy-2.0/site-packages``, and +the scripts in ``pypy-2.0/bin``. Installing using virtualenv --- diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst --- a/pypy/doc/index.rst +++ b/pypy/doc/index.rst @@ -40,7 +40,7 @@ * `FAQ`_: some frequently asked questions. -* `Release 2.0 beta 2`_: the latest official release +* `Release 2.0`_: the latest official release * `PyPy Blog`_: news and status info about PyPy @@ -110,7 +110,7 @@ .. _`Getting Started`: getting-started.html .. _`Papers`: extradoc.html .. _`Videos`: video-index.html -.. _`Release 2.0 beta 2`: http://pypy.org/download.html +.. _`Release 2.0`: http://pypy.org/download.html .. _`speed.pypy.org`: http://speed.pypy.org .. _`RPython toolchain`: translation.html .. _`potential project ideas`: project-ideas.html ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs to mention new dir layout
Author: Maciej Fijalkowski fij...@gmail.com
Branch:
Changeset: r60911:d52661180965
Date: 2013-02-06 20:53 +0200
http://bitbucket.org/pypy/pypy/changeset/d52661180965/
Log:update docs to mention new dir layout
diff --git a/pypy/doc/arm.rst b/pypy/doc/arm.rst
--- a/pypy/doc/arm.rst
+++ b/pypy/doc/arm.rst
@@ -145,7 +145,7 @@
::
- pypy ~/path_to_pypy_checkout/pypy/translator/goal/translate.py -O1
--platform=arm target.py
+ pypy ~/path_to_pypy_checkout/rpython/translator/goal/translate.py -O1
--platform=arm target.py
If everything worked correctly this should yield an ARM binary. Running this
binary in the ARM chroot or on an ARM device should produce the output ``Hello
World``.
diff --git a/pypy/doc/cppyy.rst b/pypy/doc/cppyy.rst
--- a/pypy/doc/cppyy.rst
+++ b/pypy/doc/cppyy.rst
@@ -86,10 +86,10 @@
$ hg clone https://bitbucket.org/pypy/pypy
$ cd pypy
$ hg up reflex-support # optional
-$ cd pypy/translator/goal
+$ cd pypy/goal
# This example shows python, but using pypy-c is faster and uses less
memory
-$ python translate.py -O jit --gcrootfinder=shadowstack
targetpypystandalone.py --withmod-cppyy
+$ python ../../rpython/bin/rpython.py -O jit --gcrootfinder=shadowstack
targetpypystandalone.py --withmod-cppyy
This will build a ``pypy-c`` that includes the cppyy module, and through that,
Reflex support.
diff --git a/pypy/doc/ctypes-implementation.rst
b/pypy/doc/ctypes-implementation.rst
--- a/pypy/doc/ctypes-implementation.rst
+++ b/pypy/doc/ctypes-implementation.rst
@@ -113,7 +113,7 @@
The pypy-c translated to run the ctypes tests can be used to run the pyglet
examples as well. They can be run like e.g.::
$ cd pyglet/
-$ PYTHONPATH=. ../ctypes-stable/pypy/translator/goal/pypy-c
examples/opengl.py
+$ PYTHONPATH=. ../ctypes-stable/pypy/goal/pypy-c examples/opengl.py
they usually should be terminated with ctrl-c. Refer to the their doc strings
for details about how they should behave.
diff --git a/pypy/doc/getting-started-dev.rst b/pypy/doc/getting-started-dev.rst
--- a/pypy/doc/getting-started-dev.rst
+++ b/pypy/doc/getting-started-dev.rst
@@ -24,7 +24,7 @@
python bin/translatorshell.py
Test snippets of translatable code are provided in the file
-``pypy/translator/test/snippet.py``, which is imported under the name
+``rpython/translator/test/snippet.py``, which is imported under the name
``snippet``. For example::
t = Translation(snippet.is_perfect_number, [int])
@@ -52,16 +52,18 @@
The graph can be turned into C code::
t.rtype()
-f = t.compile_c()
+lib = t.compile_c()
The first command replaces the operations with other low level versions that
-only use low level types that are available in C (e.g. int). To try out the
-compiled version::
+only use low level types that are available in C (e.g. int). The compiled
+version is now in a ``.so`` library. You can run it say using ctypes:
+from ctypes import CDLL
+f = CDLL(lib)
f(5)
- False
+ 0
f(6)
- True
+ 1
Translating the flow graph to CLI or JVM code
+
@@ -108,7 +110,7 @@
There is a small-to-medium demo showing the translator and the annotator::
cd demo
-../pypy/translator/goal/translate.py --view --annotate bpnn.py
+../rpython/translator/goal/translate.py --view --annotate bpnn.py
This causes ``bpnn.py`` to display itself as a call graph and class
hierarchy. Clicking on functions shows the flow graph of the particular
@@ -119,17 +121,17 @@
To turn this example to C code (compiled to the executable ``bpnn-c``),
type simply::
-../pypy/translator/goal/translate.py bpnn.py
+../rpython/translator/goal/translate.py bpnn.py
Translating Full Programs
+
To translate full RPython programs, there is the script ``translate.py`` in
-``translator/goal``. Examples for this are a slightly changed version of
+``rpython/translator/goal``. Examples for this are a slightly changed version
of
Pystone::
-cd pypy/translator/goal
+cd rpython/translator/goal
python translate.py targetrpystonedalone
This will produce the executable targetrpystonedalone-c.
diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst
--- a/pypy/doc/index.rst
+++ b/pypy/doc/index.rst
@@ -220,9 +220,8 @@
===
Directory explanation/links
===
-`pypy/annotation/`_`type inferencing code`_ for `RPython`_
programs
-`pypy/bin/`_ command-line scripts, mainly `py.py`_ and
`translatorshell.py`_
+`pypy/bin/`_ command-line scripts, mainly
`pyinteractive.py`_
`pypy/config/`_handles the numerous options for building
and running PyPy
@@ -249,20 +248,8 @@
[pypy-commit] pypy default: update docs (bwesterb)
Author: mattip matti.pi...@gmail.com Branch: Changeset: r60343:6018156230ed Date: 2013-01-22 17:10 +0200 http://bitbucket.org/pypy/pypy/changeset/6018156230ed/ Log:update docs (bwesterb) diff --git a/pypy/doc/arm.rst b/pypy/doc/arm.rst --- a/pypy/doc/arm.rst +++ b/pypy/doc/arm.rst @@ -130,15 +130,7 @@ export SB2=/srv/chroot/precise_arm export SB2OPT='-t ARM' -Once this is set, you can call the translator - -:: - - pypy ~/path_to_pypy_checkout/pypy/translator/goal/translate.py -O1 --platform=arm target.py - -If everything worked correctly this should yield an ARM binary. Running this binary in the ARM chroot or on an ARM device should produce the output ``Hello World``. - -.. _`this`: +Once this is set, you can call the translator. For example save this file :: @@ -148,3 +140,22 @@ def target(*args): return main, None + +and call the translator + +:: + + pypy ~/path_to_pypy_checkout/pypy/translator/goal/translate.py -O1 --platform=arm target.py + +If everything worked correctly this should yield an ARM binary. Running this binary in the ARM chroot or on an ARM device should produce the output ``Hello World``. + +To translate the full python pypy interpreter, you can cd into pypy/goal and call + +:: + + pypy path to rpython/rpython/translator/goal/translate.py -O1 --platform=arm --gcrootfinder=shadowstack --jit-backend=arm targetpypystandalone.py + +The gcrootfinder option is needed to work around `issue 1377`_ and the jit-backend works around `issue 1376`_ + +.. _`issue 1377`: https://bugs.pypy.org/issue1377 +.. _`issue 1376`: https://bugs.pypy.org/issue1376 ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs
Author: Maciej Fijalkowski fij...@gmail.com Branch: Changeset: r59029:0cd89b0c4c81 Date: 2012-11-22 12:49 +0100 http://bitbucket.org/pypy/pypy/changeset/0cd89b0c4c81/ Log:update docs diff --git a/pypy/doc/conf.py b/pypy/doc/conf.py --- a/pypy/doc/conf.py +++ b/pypy/doc/conf.py @@ -45,9 +45,9 @@ # built documents. # # The short X.Y version. -version = '1.9' +version = '2.0' # The full version, including alpha/beta/rc tags. -release = '1.9' +release = '2.0-beta1' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/pypy/doc/getting-started-python.rst b/pypy/doc/getting-started-python.rst --- a/pypy/doc/getting-started-python.rst +++ b/pypy/doc/getting-started-python.rst @@ -103,8 +103,8 @@ executable. The executable behaves mostly like a normal Python interpreter:: $ ./pypy-c -Python 2.7.2 (341e1e3821ff, Jun 07 2012, 15:40:31) -[PyPy 1.9.0 with GCC 4.4.3] on linux2 +Python 2.7.3 (7e4f0faa3d51, Nov 22 2012, 10:35:18) +[PyPy 2.0.0-beta1 with GCC 4.7.1] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``RPython magically makes you rich and famous (says so on the tin)'' @@ -234,7 +234,7 @@ the ``bin/pypy`` executable. To install PyPy system wide on unix-like systems, it is recommended to put the -whole hierarchy alone (e.g. in ``/opt/pypy1.9``) and put a symlink to the +whole hierarchy alone (e.g. in ``/opt/pypy2.0-beta1``) and put a symlink to the ``pypy`` executable into ``/usr/bin`` or ``/usr/local/bin`` If the executable fails to find suitable libraries, it will report diff --git a/pypy/doc/getting-started.rst b/pypy/doc/getting-started.rst --- a/pypy/doc/getting-started.rst +++ b/pypy/doc/getting-started.rst @@ -53,15 +53,14 @@ PyPy is ready to be executed as soon as you unpack the tarball or the zip file, with no need to install it in any specific location:: -$ tar xf pypy-1.9-linux.tar.bz2 -$ ./pypy-1.9/bin/pypy -Python 2.7.2 (341e1e3821ff, Jun 07 2012, 15:40:31) -[PyPy 1.9.0 with GCC 4.4.3] on linux2 +$ tar xf pypy-2.0-beta1-linux.tar.bz2 +$ ./pypy-2.0-beta1/bin/pypy +Python 2.7.3 (7e4f0faa3d51, Nov 22 2012, 10:35:18) +[PyPy 2.0.0-beta1 with GCC 4.7.1] on linux2 Type help, copyright, credits or license for more information. -And now for something completely different: ``it seems to me that once you -settle on an execution / object model and / or bytecode format, you've already -decided what languages (where the 's' seems superfluous) support is going to be -first class for'' +And now for something completely different: ``PyPy is an exciting technology +that lets you to write fast, portable, multi-platform interpreters with less +effort'' If you want to make PyPy available system-wide, you can put a symlink to the @@ -76,14 +75,14 @@ $ curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py -$ ./pypy-1.9/bin/pypy distribute_setup.py +$ ./pypy-2.0-beta1/bin/pypy distribute_setup.py -$ ./pypy-1.9/bin/pypy get-pip.py +$ ./pypy-2.0-beta1/bin/pypy get-pip.py -$ ./pypy-1.9/bin/pip install pygments # for example +$ ./pypy-2.0-beta1/bin/pip install pygments # for example -3rd party libraries will be installed in ``pypy-1.9/site-packages``, and -the scripts in ``pypy-1.9/bin``. +3rd party libraries will be installed in ``pypy-2.0-beta1/site-packages``, and +the scripts in ``pypy-2.0-beta1/bin``. Installing using virtualenv --- diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst --- a/pypy/doc/index.rst +++ b/pypy/doc/index.rst @@ -15,7 +15,7 @@ * `FAQ`_: some frequently asked questions. -* `Release 1.9`_: the latest official release +* `Release 2.0 beta 1`_: the latest official release * `PyPy Blog`_: news and status info about PyPy @@ -75,7 +75,7 @@ .. _`Getting Started`: getting-started.html .. _`Papers`: extradoc.html .. _`Videos`: video-index.html -.. _`Release 1.9`: http://pypy.org/download.html +.. _`Release 2.0 beta1`: http://pypy.org/download.html .. _`speed.pypy.org`: http://speed.pypy.org .. _`RPython toolchain`: translation.html .. _`potential project ideas`: project-ideas.html @@ -120,9 +120,9 @@ Windows, on top of .NET, and on top of Java. To dig into PyPy it is recommended to try out the current Mercurial default branch, which is always working or mostly working, -instead of the latest release, which is `1.9`__. +instead of the latest release, which is `2.0 beta1`__. -.. __: release-1.9.0.html +.. __: release-2.0.0-beta1.html PyPy is mainly developed on Linux and Mac OS X. Windows is supported, but platform-specific bugs tend to take longer before we notice and fix ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs
Author: Maciej Fijalkowski fij...@gmail.com Branch: Changeset: r55498:a0aabbd71c1d Date: 2012-06-08 11:34 +0200 http://bitbucket.org/pypy/pypy/changeset/a0aabbd71c1d/ Log:update docs diff --git a/pypy/doc/conf.py b/pypy/doc/conf.py --- a/pypy/doc/conf.py +++ b/pypy/doc/conf.py @@ -45,9 +45,9 @@ # built documents. # # The short X.Y version. -version = '1.8' +version = '1.9' # The full version, including alpha/beta/rc tags. -release = '1.8' +release = '1.9' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/pypy/doc/getting-started-python.rst b/pypy/doc/getting-started-python.rst --- a/pypy/doc/getting-started-python.rst +++ b/pypy/doc/getting-started-python.rst @@ -103,10 +103,12 @@ executable. The executable behaves mostly like a normal Python interpreter:: $ ./pypy-c -Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03) -[PyPy 1.8.0 with GCC 4.4.3] on linux2 +Python 2.7.2 (341e1e3821ff, Jun 07 2012, 15:40:31) +[PyPy 1.9.0 with GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. -And now for something completely different: ``this sentence is false'' +And now for something completely different: ``RPython magically makes you rich +and famous (says so on the tin)'' + 46 - 4 42 from test import pystone diff --git a/pypy/doc/getting-started.rst b/pypy/doc/getting-started.rst --- a/pypy/doc/getting-started.rst +++ b/pypy/doc/getting-started.rst @@ -53,10 +53,10 @@ PyPy is ready to be executed as soon as you unpack the tarball or the zip file, with no need to install it in any specific location:: -$ tar xf pypy-1.8-linux.tar.bz2 -$ ./pypy-1.8/bin/pypy -Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03) -[PyPy 1.8.0 with GCC 4.4.3] on linux2 +$ tar xf pypy-1.9-linux.tar.bz2 +$ ./pypy-1.9/bin/pypy +Python 2.7.2 (341e1e3821ff, Jun 07 2012, 15:40:31) +[PyPy 1.9.0 with GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``it seems to me that once you settle on an execution / object model and / or bytecode format, you've already @@ -76,14 +76,14 @@ $ curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py -$ ./pypy-1.8/bin/pypy distribute_setup.py +$ ./pypy-1.9/bin/pypy distribute_setup.py -$ ./pypy-1.8/bin/pypy get-pip.py +$ ./pypy-1.9/bin/pypy get-pip.py -$ ./pypy-1.8/bin/pip install pygments # for example +$ ./pypy-1.9/bin/pip install pygments # for example -3rd party libraries will be installed in ``pypy-1.8/site-packages``, and -the scripts in ``pypy-1.8/bin``. +3rd party libraries will be installed in ``pypy-1.9/site-packages``, and +the scripts in ``pypy-1.9/bin``. Installing using virtualenv --- diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst --- a/pypy/doc/index.rst +++ b/pypy/doc/index.rst @@ -15,7 +15,7 @@ * `FAQ`_: some frequently asked questions. -* `Release 1.8`_: the latest official release +* `Release 1.9`_: the latest official release * `PyPy Blog`_: news and status info about PyPy @@ -75,7 +75,7 @@ .. _`Getting Started`: getting-started.html .. _`Papers`: extradoc.html .. _`Videos`: video-index.html -.. _`Release 1.8`: http://pypy.org/download.html +.. _`Release 1.9`: http://pypy.org/download.html .. _`speed.pypy.org`: http://speed.pypy.org .. _`RPython toolchain`: translation.html .. _`potential project ideas`: project-ideas.html @@ -120,9 +120,9 @@ Windows, on top of .NET, and on top of Java. To dig into PyPy it is recommended to try out the current Mercurial default branch, which is always working or mostly working, -instead of the latest release, which is `1.8`__. +instead of the latest release, which is `1.9`__. -.. __: release-1.8.0.html +.. __: release-1.9.0.html PyPy is mainly developed on Linux and Mac OS X. Windows is supported, but platform-specific bugs tend to take longer before we notice and fix ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs version
Author: Maciej Fijalkowski fij...@gmail.com Branch: Changeset: r52315:a4aa0c1a1241 Date: 2012-02-09 18:27 +0200 http://bitbucket.org/pypy/pypy/changeset/a4aa0c1a1241/ Log:update docs version diff --git a/pypy/doc/getting-started.rst b/pypy/doc/getting-started.rst --- a/pypy/doc/getting-started.rst +++ b/pypy/doc/getting-started.rst @@ -53,11 +53,10 @@ PyPy is ready to be executed as soon as you unpack the tarball or the zip file, with no need to install it in any specific location:: -$ tar xf pypy-1.7-linux.tar.bz2 - -$ ./pypy-1.7/bin/pypy -Python 2.7.1 (?, Apr 27 2011, 12:44:21) -[PyPy 1.7.0 with GCC 4.4.3] on linux2 +$ tar xf pypy-1.8-linux.tar.bz2 +$ ./pypy-1.8/bin/pypy +Python 2.7.1 (48ebdce33e1b, Feb 09 2012, 00:55:31) +[PyPy 1.8.0 with GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``implementing LOGO in LOGO: turtles all the way down'' @@ -75,14 +74,14 @@ $ curl -O https://raw.github.com/pypa/pip/master/contrib/get-pip.py -$ ./pypy-1.7/bin/pypy distribute_setup.py +$ ./pypy-1.8/bin/pypy distribute_setup.py -$ ./pypy-1.7/bin/pypy get-pip.py +$ ./pypy-1.8/bin/pypy get-pip.py -$ ./pypy-1.7/bin/pip install pygments # for example +$ ./pypy-1.8/bin/pip install pygments # for example -3rd party libraries will be installed in ``pypy-1.7/site-packages``, and -the scripts in ``pypy-1.7/bin``. +3rd party libraries will be installed in ``pypy-1.8/site-packages``, and +the scripts in ``pypy-1.8/bin``. Installing using virtualenv --- diff --git a/pypy/doc/index.rst b/pypy/doc/index.rst --- a/pypy/doc/index.rst +++ b/pypy/doc/index.rst @@ -15,7 +15,7 @@ * `FAQ`_: some frequently asked questions. -* `Release 1.7`_: the latest official release +* `Release 1.8`_: the latest official release * `PyPy Blog`_: news and status info about PyPy @@ -75,7 +75,7 @@ .. _`Getting Started`: getting-started.html .. _`Papers`: extradoc.html .. _`Videos`: video-index.html -.. _`Release 1.7`: http://pypy.org/download.html +.. _`Release 1.8`: http://pypy.org/download.html .. _`speed.pypy.org`: http://speed.pypy.org .. _`RPython toolchain`: translation.html .. _`potential project ideas`: project-ideas.html @@ -120,9 +120,9 @@ Windows, on top of .NET, and on top of Java. To dig into PyPy it is recommended to try out the current Mercurial default branch, which is always working or mostly working, -instead of the latest release, which is `1.7`__. +instead of the latest release, which is `1.8`__. -.. __: release-1.7.0.html +.. __: release-1.8.0.html PyPy is mainly developed on Linux and Mac OS X. Windows is supported, but platform-specific bugs tend to take longer before we notice and fix diff --git a/pypy/module/sys/version.py b/pypy/module/sys/version.py --- a/pypy/module/sys/version.py +++ b/pypy/module/sys/version.py @@ -7,7 +7,7 @@ from pypy.interpreter import gateway #XXX # the release serial 42 is not in range(16) -CPYTHON_VERSION= (2, 7, 1, final, 42) #XXX # sync patchlevel.h +CPYTHON_VERSION= (2, 7, 2, final, 42) #XXX # sync patchlevel.h CPYTHON_API_VERSION= 1013 #XXX # sync with include/modsupport.h PYPY_VERSION = (1, 8, 1, dev, 0)#XXX # sync patchlevel.h ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
[pypy-commit] pypy default: update docs
Author: Maciej Fijalkowski fij...@gmail.com Branch: Changeset: r52335:5e8590c7ed02 Date: 2012-02-09 23:16 +0200 http://bitbucket.org/pypy/pypy/changeset/5e8590c7ed02/ Log:update docs diff --git a/pypy/doc/getting-started-python.rst b/pypy/doc/getting-started-python.rst --- a/pypy/doc/getting-started-python.rst +++ b/pypy/doc/getting-started-python.rst @@ -103,18 +103,22 @@ executable. The executable behaves mostly like a normal Python interpreter:: $ ./pypy-c -Python 2.7.0 (61ef2a11b56a, Mar 02 2011, 03:00:11) -[PyPy 1.6.0 with GCC 4.4.3] on linux2 +Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03) +[PyPy 1.8.0 with GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. And now for something completely different: ``this sentence is false'' 46 - 4 42 from test import pystone pystone.main() -Pystone(1.1) time for 5 passes = 0.280017 -This machine benchmarks at 178561 pystones/second - +Pystone(1.1) time for 5 passes = 0.220015 +This machine benchmarks at 227257 pystones/second + pystone.main() +Pystone(1.1) time for 5 passes = 0.060004 +This machine benchmarks at 833278 pystones/second + +Note that pystone gets faster as the JIT kicks in. This executable can be moved around or copied on other machines; see Installation_ below. diff --git a/pypy/doc/getting-started.rst b/pypy/doc/getting-started.rst --- a/pypy/doc/getting-started.rst +++ b/pypy/doc/getting-started.rst @@ -55,11 +55,13 @@ $ tar xf pypy-1.8-linux.tar.bz2 $ ./pypy-1.8/bin/pypy -Python 2.7.1 (48ebdce33e1b, Feb 09 2012, 00:55:31) +Python 2.7.2 (0e28b379d8b3, Feb 09 2012, 19:41:03) [PyPy 1.8.0 with GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. -And now for something completely different: ``implementing LOGO in LOGO: -turtles all the way down'' +And now for something completely different: ``it seems to me that once you +settle on an execution / object model and / or bytecode format, you've already +decided what languages (where the 's' seems superfluous) support is going to be +first class for'' If you want to make PyPy available system-wide, you can put a symlink to the ___ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
