\date{\today} % XXX update before final release!
\release{2.3} % software release, not documentation
-\setreleaseinfo{b1} % empty for final release
+\setreleaseinfo{b1+} % empty for final release
\setshortversion{2.3} % major.minor only for software
Historically, most, but not all, Python releases have also been
GPL-compatible; the table below summarizes the various releases.
-\begin{tablev}{c|c|c|c|c}{textrm}{Release}{Derived from}{Year}{Owner}{GPL compatible?}
+\begin{tablev}{c|c|c|c|c}{textrm}%
+ {Release}{Derived from}{Year}{Owner}{GPL compatible?}
\linev{0.9.0 thru 1.2}{n/a}{1991-1995}{CWI}{yes}
\linev{1.3 thru 1.5.2}{1.2}{1995-1999}{CNRI}{yes}
\linev{1.6}{1.5.2}{2000}{CNRI}{no}
\linev{2.1.2}{2.1.1}{2002}{PSF}{yes}
\linev{2.1.3}{2.1.2}{2002}{PSF}{yes}
\linev{2.2.1}{2.2}{2002}{PSF}{yes}
+ \linev{2.2.2}{2.2.1}{2002}{PSF}{yes}
+ \linev{2.3}{2.2.2}{2002-2003}{PSF}{yes}
\end{tablev}
\note{GPL-compatible doesn't mean that we're distributing
\section{Terms and conditions for accessing or otherwise using Python}
-\centerline{\strong{PSF LICENSE AGREEMENT FOR PYTHON 2.3}}
+\centerline{\strong{PSF LICENSE AGREEMENT FOR PYTHON \version}}
\begin{enumerate}
\item
prepare derivative works, distribute, and otherwise use Python
\version{} alone or in any derivative version, provided, however, that
PSF's License Agreement and PSF's notice of copyright, i.e.,
-``Copyright \copyright{} 2001, 2002 Python Software Foundation; All
+``Copyright \copyright{} 2001-2003 Python Software Foundation; All
Rights Reserved'' are retained in Python \version{} alone or in any
derivative version prepared by Licensee.