[Python-checkins] python/dist/src/Doc/lib libtime.tex,1.57,1.58
bcannon@users.sourceforge.net
bcannon@users.sourceforge.net
Mon, 30 Jun 2003 22:16:10 -0700
Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1:/tmp/cvs-serv13084/Doc/lib
Modified Files:
libtime.tex
Log Message:
Make temporary change of using _strptime for time.strptime permanent.
Flesh out docs to better explain time.strptime (closes bug #697990).
Index: libtime.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libtime.tex,v
retrieving revision 1.57
retrieving revision 1.58
diff -C2 -d -r1.57 -r1.58
*** libtime.tex 8 Jun 2003 13:57:19 -0000 1.57
--- libtime.tex 1 Jul 2003 05:16:08 -0000 1.58
***************
*** 289,300 ****
directives as those used by \function{strftime()}; it defaults to
\code{"\%a \%b \%d \%H:\%M:\%S \%Y"} which matches the formatting
! returned by \function{ctime()}. The same platform caveats apply; see
! the local \UNIX{} documentation for restrictions or additional
! supported directives. If \var{string} cannot be parsed according to
! \var{format}, \exception{ValueError} is raised. Values which are not
! provided as part of the input string are filled in with default
! values; the specific values are platform-dependent as the XPG standard
! does not provide sufficient information to constrain the result.
! \end{funcdesc}
\begin{datadesc}{struct_time}
--- 289,303 ----
directives as those used by \function{strftime()}; it defaults to
\code{"\%a \%b \%d \%H:\%M:\%S \%Y"} which matches the formatting
! returned by \function{ctime()}. If \var{string} cannot be parsed
! according to \var{format}, \exception{ValueError} is raised. If the
! string to be parsed has excess data after parsing,
! \exception{ValueError} is raised. The default values used to fill in
! any missing data is \code{(1900, 1, 1, 0, 0, 0, 0, 1, -1)} .
!
! Support for the \code{\%Z} directive is based on the values contained in
! \code{tzname} and whether \code{daylight} is true. Because of this
! it is platform-specifc sans recognition for UTC and GMT which are
! always known (and are considered to be non-daylight savings
! timezones).
\begin{datadesc}{struct_time}