[pypy-svn] r72116 - pypy/extradoc/pypy.org
fijal at codespeak.net
fijal at codespeak.net
Thu Mar 11 18:20:51 CET 2010
Author: fijal
Date: Thu Mar 11 18:20:50 2010
New Revision: 72116
Modified:
pypy/extradoc/pypy.org/download.html
pypy/extradoc/pypy.org/features.html
Log:
update html
Modified: pypy/extradoc/pypy.org/download.html
==============================================================================
--- pypy/extradoc/pypy.org/download.html (original)
+++ pypy/extradoc/pypy.org/download.html Thu Mar 11 18:20:50 2010
@@ -70,9 +70,9 @@
them do, nowadays), as well as on any <a class="reference external" href="http://en.wikipedia.org/wiki/X86-64">x86-64</a> machine in the 32-bit
compatibility mode.</p>
<ul class="simple">
-<li>Linux binary</li>
-<li>Mac OS/X binary</li>
-<li>Windows binary</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-linux.tar.bz2">Linux binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-osx.tar.bz2">Mac OS/X binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-win.zip">Windows binary</a></li>
</ul>
<p>If your CPU is really old, it may not have SSE2. In this case, you need
to <a class="reference internal" href="#translate">translate</a> yourself with the option <tt class="docutils literal"><span class="pre">--jit-backend=x86-without-sse2</span></tt>.</p>
@@ -81,20 +81,20 @@
<p>If you want to help us with implementing the 64-bit JIT backend,
<a class="reference external" href="contact.html">contact us</a>!</p>
</div>
-<div class="section" id="id1">
+<div class="section" id="id4">
<span id="no-jit-version"></span><span id="with-no-jit-compiler"></span><h1>“No JIT” version</h1>
<p><strong>WARNING!</strong> Unless you really want to try this out, we recommend the JIT
version.</p>
<p>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 <tt class="docutils literal"><span class="pre">pypy-c</span></tt> runs them
+least a few hundred MBs), the following version of <tt class="docutils literal"><span class="pre">pypy-nojit</span></tt> runs them
by requiring generally 1.5x or 2x less memory than CPython. These
binaries work on 32-bit <a class="reference external" href="http://en.wikipedia.org/wiki/IA-32">x86 (IA-32)</a> CPUs as well as <a class="reference external" href="http://en.wikipedia.org/wiki/X86-64">x86-64</a> CPUs
in the 32-bit compatibility mode.</p>
<ul class="simple">
-<li>Linux binary</li>
-<li>Mac OS/X binary</li>
-<li>Windows binary</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-linux-nojit.tar.bz2">Linux binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-osx-nojit.tar.bz2">Mac OS/X binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-win-nojit.zip">Windows binary</a></li>
</ul>
<p>If your CPU is a 64-bit machine and you want to <a class="reference internal" href="#translate">translate</a> a 32-bit
version of PyPy yourself, <a class="reference internal" href="#here-are-hints">here are hints</a>.</p>
@@ -109,9 +109,9 @@
binaries work on 32-bit <a class="reference external" href="http://en.wikipedia.org/wiki/IA-32">x86 (IA-32)</a> CPUs as well as <a class="reference external" href="http://en.wikipedia.org/wiki/X86-64">x86-64</a> CPUs
in the 32-bit compatibility mode.</p>
<ul class="simple">
-<li>Linux binary</li>
-<li>Mac OS/X binary</li>
-<li>Windows binary</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-linux-sandbox.bz2">Linux binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-osx-sandbox.bz2">Mac OS/X binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-win-sandbox.zip">Windows binary</a></li>
</ul>
<p>It is also possible to <a class="reference internal" href="#translate">translate</a> a version that includes both
sandboxing and the JIT compiler, although as the JIT is relatively
@@ -121,15 +121,15 @@
<p>The native 64-bit version needs testing and careful reviewing;
<a class="reference external" href="contact.html">contact us</a>!</p>
</div>
-<div class="section" id="id2">
+<div class="section" id="id11">
<span id="stackless-version"></span><h1>“Stackless” version</h1>
<p>Provides <a class="reference external" href="http://www.stackless.com/">Stackless</a> extensions, as well as <a class="reference external" href="http://codespeak.net/svn/greenlet/trunk/doc/greenlet.txt">greenlets</a>. These
binaries work on 32-bit <a class="reference external" href="http://en.wikipedia.org/wiki/IA-32">x86 (IA-32)</a> CPUs as well as <a class="reference external" href="http://en.wikipedia.org/wiki/X86-64">x86-64</a> CPUs
in the 32-bit compatibility mode.</p>
<ul class="simple">
-<li>Linux binary</li>
-<li>Mac OS/X binary</li>
-<li>Windows binary</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-linux-stackless.tar.bz2">Linux binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-osx-stackless.tar.bz2">Mac OS/X binary</a></li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-win-stackless.zip">Windows binary</a></li>
</ul>
<p>It is not possible right now to combine Stackless features with the JIT.</p>
<p>If your CPU is a 64-bit machine and you want to <a class="reference internal" href="#translate">translate</a> a 32-bit
@@ -142,7 +142,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:</p>
<pre class="literal-block">
-/usr/bin/pypy-c
+/usr/bin/pypy
/usr/share/pypy-1.2/lib-python/*
/usr/share/pypy-1.2/pypy/*
</pre>
@@ -152,10 +152,10 @@
<span id="translate"></span><h1>Building from source</h1>
<ol class="arabic">
<li><p class="first">Get the source code. The following packages contain the source at
-the same revision as the above binaries:</p>
+the same revision as the above binaries (these are svn exports):</p>
<ul class="simple">
-<li>pypy-1.2-src.tar.bz2 (sources, Unix line endings)</li>
-<li>pypy-1.2-src.zip (sources, Windows line endings)</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-src.tar.bz2">pypy-1.2-src.tar.bz2</a> (sources, Unix line endings)</li>
+<li><a class="reference external" href="http://pypy.org/download/pypy-1.2-src.zip">pypy-1.2-src.zip</a> (sources, Windows line endings)</li>
</ul>
<p>Or you can checkout the current trunk using <a class="reference external" href="http://subversion.tigris.org/">Subversion</a> (the trunk
usually works and is of course more up-to-date):</p>
Modified: pypy/extradoc/pypy.org/features.html
==============================================================================
--- pypy/extradoc/pypy.org/features.html (original)
+++ pypy/extradoc/pypy.org/features.html Thu Mar 11 18:20:50 2010
@@ -104,9 +104,9 @@
<p>PyPy has many secondary features and semi-independent
projects. We will mention here:</p>
<ul class="simple">
-<li><strong>the .NET backend:</strong> you get a version of <tt class="docutils literal"><span class="pre">pypy-c</span></tt> that runs
+<li><strong>the .NET backend:</strong> you get a version of <tt class="docutils literal"><span class="pre">pypy-net</span></tt> that runs
natively in the .NET/CLI VM. Of particular interest is <a class="reference external" href="http://codespeak.net/svn/pypy/branch/cli-jit/">the cli-jit
-branch</a>, in which you can make a version of <tt class="docutils literal"><span class="pre">pypy-c</span></tt> which also
+branch</a>, in which you can make a version of <tt class="docutils literal"><span class="pre">pypy-net</span></tt> 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).</li>
More information about the Pypy-commit
mailing list