From: Andrew M. Kuchling <amk@amk.ca>
Date: Sat, 1 Jul 2000 00:14:43 +0000 (+0000)
Subject: Update the version number in an example
X-Git-Tag: v2.0b1~1172
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8357c4c9c6ce60336c625ae75ce8b07194213c4e;p=thirdparty%2FPython%2Fcpython.git

Update the version number in an example
---

diff --git a/Doc/whatsnew/whatsnew20.tex b/Doc/whatsnew/whatsnew20.tex
index 08ce67e07022..817251867590 100644
--- a/Doc/whatsnew/whatsnew20.tex
+++ b/Doc/whatsnew/whatsnew20.tex
@@ -530,15 +530,16 @@ f()
 A new variable holding more detailed version information has been
 added to the \module{sys} module.  \code{sys.version_info} is a tuple
 \code{(\var{major}, \var{minor}, \var{micro}, \var{level},
-\var{serial})} For example, in 2.0a2 \code{sys.version_info} is
-\code{(1, 6, 0, 'alpha', 2)}.  \var{level} is a string such as
-\code{"alpha"}, \code{"beta"}, or \code{""} for a final release.
+\var{serial})} For example, in a hypothetical 2.0.1beta1,
+\code{sys.version_info} would be \code{(2, 0, 1, 'beta', 1)}.
+\var{level} is a string such as \code{"alpha"}, \code{"beta"}, or
+\code{""} for a final release.
 
 % ======================================================================
 \section{Extending/Embedding Changes}
 
 Some of the changes are under the covers, and will only be apparent to
-people writing C extension modules, or embedding a Python interpreter
+people writing C extension modules or embedding a Python interpreter
 in a larger application.  If you aren't dealing with Python's C API,
 you can safely skip this section.