traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update change to version_info structure.

This commit is contained in:
Fred Drake 2000-04-13 17:51:58 +00:00
parent 93a20bf87c
commit 9cf7587fdc
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Doc/lib/libsys.tex
View File

@ -327,12 +327,13 @@ directories (where appropriate on each platform). An example:
\end{datadesc}
\begin{datadesc}{version_info}
A tuple containing the four components of the version number:
\var{major}, \var{minor}, \var{micro} as integers, and
\var{releaselevel} as a string. The \var{releaselevel} value will be
an empty string for a final release. The \code{version_info} value
corresponding to the \code{version} string shown above is
\code{(1, 5, 2, '')}.
A tuple containing the five components of the version number:
\var{major}, \var{minor}, \var{micro}, \var{releaselevel}, and
\var{serial}. All values except \var{releaselevel} are integers; the
release level is \code{'alpha'}, \code{'beta'},
\code{'candidate'}, or \code{'final'}. The \code{version_info} value
corresponding to the Python version 1.6 is
\code{(1, 6, 0, 'final', 0)}.
\versionadded{1.6}
\end{datadesc}