-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.351 2010/08/17 04:37:20 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.352 2010/09/08 20:35:51 petere Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
<listitem>
<para>
Full path to the Python interpreter. This will be used to
- determine the dependencies for building PL/Python.
+ determine the dependencies for building PL/Python. Also,
+ whether Python 2 or 3 is specified here (or otherwise
+ implicitly chosen) determines which variant of the PL/Python
+ language becomes available. See
+ <![%standalone-include[the <application>PL/Python</>
+ documentation]]>
+ <![%standalone-ignore[<xref linkend="plpython-python23">]]>
+ for more information.
</para>
</listitem>
</varlistentry>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.52 2010/08/05 18:36:33 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plpython.sgml,v 1.53 2010/09/08 20:35:51 petere Exp $ -->
<chapter id="plpython">
<title>PL/Python - Python Procedural Language</title>
whether PL/Python for Python 2 or Python 3 or both are available.
</para>
+ <tip>
+ <para>
+ The built variant depends on which Python version was found during
+ the installation or which version was explicitly set using
+ the <envar>PYTHON</envar> environment variable;
+ see <xref linkend="install-procedure">. To make both variants of
+ PL/Python available in one installation, the source tree has to be
+ configured and built twice.
+ </para>
+ </tip>
+
<para>
This results in the following usage and migration strategy:
<para>
See also the
- document <ulink url="http://docs.python.org/dev/3.0/whatsnew/3.0.html">What's
+ document <ulink url="http://docs.python.org/py3k/whatsnew/3.0.html">What's
New In Python 3.0</ulink> for more information about porting to
Python 3.
</para>