diff --git a/source/download.txt b/source/download.txt index fc000028f68cb025d3cd540d343007767c18391a_c291cmNlL2Rvd25sb2FkLnR4dA==..a0176534f20982c956d8377beb193e76787be20c_c291cmNlL2Rvd25sb2FkLnR4dA== 100644 --- a/source/download.txt +++ b/source/download.txt @@ -34,9 +34,13 @@ them do, nowadays), as well as on any `x86-64`_ machine in the 32-bit compatibility mode. -* Linux binary -* Mac OS/X binary -* Windows binary +* `Linux binary`__ +* `Mac OS/X binary`__ +* `Windows binary`__ + +.. __: http://pypy.org/download/pypy-1.2-linux.tar.bz2 +.. __: http://pypy.org/download/pypy-1.2-osx.tar.bz2 +.. __: http://pypy.org/download/pypy-1.2-win.zip If your CPU is really old, it may not have SSE2. In this case, you need to translate_ yourself with the option ``--jit-backend=x86-without-sse2``. @@ -59,8 +63,8 @@ This version still has a few advantages over the JIT Compiler version. Notably, for Python programs that require large amounts of memory (at -least a few hundred MBs), the following version of ``pypy-c`` runs them +least a few hundred MBs), the following version of ``pypy-nojit`` runs them by requiring generally 1.5x or 2x less memory than CPython. These binaries work on 32-bit `x86 (IA-32)`_ CPUs as well as `x86-64`_ CPUs in the 32-bit compatibility mode. @@ -63,10 +67,14 @@ by requiring generally 1.5x or 2x less memory than CPython. These binaries work on 32-bit `x86 (IA-32)`_ CPUs as well as `x86-64`_ CPUs in the 32-bit compatibility mode. -* Linux binary -* Mac OS/X binary -* Windows binary +* `Linux binary`__ +* `Mac OS/X binary`__ +* `Windows binary`__ + +.. __: http://pypy.org/download/pypy-nojit-1.2-linux.tar.bz2 +.. __: http://pypy.org/download/pypy-nojit-1.2-osx.tar.bz2 +.. __: http://pypy.org/download/pypy-nojit-1.2-win.zip If your CPU is a 64-bit machine and you want to translate_ a 32-bit version of PyPy yourself, `here are hints`_. @@ -86,9 +94,13 @@ binaries work on 32-bit `x86 (IA-32)`_ CPUs as well as `x86-64`_ CPUs in the 32-bit compatibility mode. -* Linux binary -* Mac OS/X binary -* Windows binary +* `Linux binary`__ +* `Mac OS/X binary`__ +* `Windows binary`__ + +.. __: http://pypy.org/download/pypy-sandbox-1.2-linux.bz2 +.. __: http://pypy.org/download/pypy-sandbox-1.2-osx.bz2 +.. __: http://pypy.org/download/pypy-sandbox-1.2-win.zip It is also possible to translate_ a version that includes both sandboxing and the JIT compiler, although as the JIT is relatively @@ -110,9 +122,13 @@ binaries work on 32-bit `x86 (IA-32)`_ CPUs as well as `x86-64`_ CPUs in the 32-bit compatibility mode. -* Linux binary -* Mac OS/X binary -* Windows binary +* `Linux binary`__ +* `Mac OS/X binary`__ +* `Windows binary`__ + +.. __: http://pypy.org/download/pypy-stackless-1.2-linux.tar.bz2 +.. __: http://pypy.org/download/pypy-stackless-1.2-osx.tar.bz2 +.. __: http://pypy.org/download/pypy-stackless-1.2-win.zip It is not possible right now to combine Stackless features with the JIT. @@ -129,7 +145,7 @@ uncompressed, they run in-place. On Linux or Mac OS/X, they can also be installed by manually moving the files in the following directories:: - /usr/bin/pypy-c + /usr/bin/pypy /usr/share/pypy-1.2/lib-python/* /usr/share/pypy-1.2/pypy/* diff --git a/source/features.txt b/source/features.txt index fc000028f68cb025d3cd540d343007767c18391a_c291cmNlL2ZlYXR1cmVzLnR4dA==..a0176534f20982c956d8377beb193e76787be20c_c291cmNlL2ZlYXR1cmVzLnR4dA== 100644 --- a/source/features.txt +++ b/source/features.txt @@ -92,5 +92,5 @@ PyPy has many secondary features and semi-independent projects. We will mention here: -* **the .NET backend:** you get a version of ``pypy-c`` that runs +* **the .NET backend:** you get a version of ``pypy-net`` that runs natively in the .NET/CLI VM. Of particular interest is `the cli-jit @@ -96,5 +96,5 @@ natively in the .NET/CLI VM. Of particular interest is `the cli-jit - branch`_, in which you can make a version of ``pypy-c`` which also + branch`_, in which you can make a version of ``pypy-net`` which also contains a high-level JIT compiler (it compiles your Python programs Just in Time into CLR bytecodes, which are in turn compiled natively by the VM).