summaryrefslogtreecommitdiffstats
path: root/Doc/lib/libtime.tex
Commit message (Collapse)AuthorAgeFilesLines
* Point out that %p has no effect on the output hour in strptime unless %I isSkip Montanaro2004-05-101-2/+6
| | | | used to parse the hour.
* Have strftime() check its time tuple argument to make sure the tuple's valuesBrett Cannon2004-03-021-1/+4
| | | | | | | | | | are within proper boundaries as specified in the docs. This can break possible code (datetime module needed changing, for instance) that uses 0 for values that need to be greater 1 or greater (month, day, and day of year). Fixes bug #897625.
* - add link to the datetime moduleFred Drake2003-12-311-0/+1
|
* Fix spacing markup and other sundries.Raymond Hettinger2003-09-081-1/+1
|
* Improve the wording a bitRaymond Hettinger2003-07-011-1/+1
|
* Fix spelling, grammar, usage, and markup.Raymond Hettinger2003-07-011-2/+3
|
* Make temporary change of using _strptime for time.strptime permanent.Brett Cannon2003-07-011-8/+11
| | | | Flesh out docs to better explain time.strptime (closes bug #697990).
* SF #735051, add time.tzset documentationNeal Norwitz2003-06-081-0/+96
|
* Refer reader to platform library docs for specific semantics.Jeremy Hylton2003-05-051-3/+6
| | | | Resolves SF bugs 697989, 697988, 697986.
* Update to better reflect the usage of struct_time instances throughout;Fred Drake2003-02-041-24/+28
| | | | | continuing to call these "time tuples" is misleading at best. Closes SF bug #671731; will backport to 2.2.x.
* Phrase repair.Guido van Rossum2002-12-311-1/+1
|
* Fixed longstanding bug in the description of strftime's %W code.Tim Peters2002-12-201-1/+1
|
* SF 639138, Ref. calendar module in time docs by John J LeeNeal Norwitz2002-11-151-0/+3
| | | | Will backport.
* Document struct_time and the field names.Fred Drake2002-11-131-14/+25
|
* Add notes to the asctime() and ctime() descriptions to make itFred Drake2002-10-301-0/+2
| | | | | explicit that locale information is not used. There wasn't anything that implied it was, but this has confused users.
* Doc patch from SF 474274 (pure Python strptime by Brett Cannon).Guido van Rossum2002-07-191-7/+0
|
* Clean up some markup cruft. A number of the macros that take noFred Drake2001-11-281-2/+2
| | | | | | | | parameters (like \UNIX) are commonly entered using an empty group to separate the markup from a following inter-word space; this is not needed when the next character is punctuation, or the markup is the last thing in the enclosing group. These cases were marked inconsistently; the empty group is now *only* used when needed.
* Add additional information on exceptions from time.mktime() and related toFred Drake2001-10-291-2/+7
| | | | | improper time tuples passed to various functions. Based on comments from Andreas Jung.
* Use the \note and \warning macros where appropriate.Fred Drake2001-10-201-4/+5
|
* indicate that mktime is platform-dependent. See SF bug 434143.Skip Montanaro2001-08-221-1/+2
|
* Improve Windows time.clock() blurb; was missing return type and unit.Tim Peters2001-08-191-4/+4
|
* Add a comment on time.time() returning non-decreasing values except whenFred Drake2001-08-051-1/+3
| | | | | | the clock is set back. This closes SF bug #447945.
* Revise the description of time.clock() so that it correctly describes theFred Drake2001-07-161-5/+11
| | | | | | Windows version of the function as well as the Unix flavor. This fixes SF bug #441357.
* Minor changes to match the style guide.Fred Drake2001-07-141-4/+5
|
* Fix up a few style nits -- avoid "e.g." and "i.e." -- these makeFred Drake2001-07-061-3/+3
| | | | | translation more difficult, as well as reading the English more difficult for non-native speakers.
* SourceForge bug #437041:Fred Drake2001-06-291-8/+8
| | | | | Use a portable format in the example that creates a timestamp suitable for use in email, also updating it and the footnote from RFC 822 to RFC 2822.
* Add versioning notes: many of the signatures changed to allow the timeFred Drake2001-04-191-0/+5
| | | | | used to be omitted (meaning use the current time) as of Python 2.1. Users who need cross-version portability need to know things like this.
* Fix markup typo in a {verbatim} environment (there should not be any!);Fred Drake2001-02-031-1/+1
| | | | caught by Eric Raymond.
* Instructive example for strftime(); how to generate RFC822 dates.Eric S. Raymond2001-01-281-0/+16
|
* Make the 'time' argument to the timemodule functions strftime, asctime,Thomas Wouters2001-01-191-12/+17
| | | | | | ctime, gmtime and localtime optional, defaulting to 'the current time' in all cases. Adjust docs, add news item. Also convert all argument-handling to METH_VARARGS. Closes SF patch #103265.
* Added warnings about platform vagaries to the strptime() documentation.Fred Drake2000-09-231-1/+9
| | | | This closes SourceForge bug #115146.
* Rob W. W. Hooft's spelling fixes for the Library Reference. I hopeThomas Wouters2000-07-161-2/+2
| | | | | | | | | SourceForge doesn't choke on this batch :-) I'm not entirely sure this is 100% correct. The patch changes an \index{persistency} to \index{presistence}, and I don't know what \index{} does. But it seems to do so persi--er, consistently, so I hope it isn't a problem.
* Correct a markup nit that caused a space to be dropped from the HTMLFred Drake2000-07-061-2/+2
| | | | | | version (actually a LaTeX2HTML bug), and clarified a sentence in the mktime() description based entirely on comments from Grant Griffin <grant.griffin@honeywell.com>.
* Change description of altzone to not refer to the "0th meridian".Fred Drake2000-06-301-2/+2
|
* Noted by Guido:Fred Drake2000-04-051-7/+7
| | | | | Fixed up descriptions of altzone and timezone not to refer to the 0th meridian, which doesn't exist. Reference is now to UTC.
* Merged changes from the 1.5.2p2 release.Fred Drake2000-04-031-41/+70
| | | | (Very rough.)
* Added disclaimer to the sleep() function.Guido van Rossum1999-08-191-0/+5
|
* Move some \index entries around so we can avoid using empty comments;Fred Drake1999-05-261-31/+25
| | | | | | empty comments trigger a bug in LaTeX2HTML. Problem reported by Gerry Wiener <gerry@ucar.edu>.
* Fix an amazing number of typos & malformed sentences reported by DetlefFred Drake1999-02-191-1/+1
| | | | Lannert <lannert@uni-duesseldorf.de>.
* Fix second description of handling 2-digit years (last item inFred Drake1999-01-191-9/+16
| | | | introductory text).
* Update the descriptions of strftime() and strptime() to avoidFred Drake1998-12-081-45/+47
| | | | confusion, and describe what the "directives" are about.
* Clarify Y2K behavior when a tuple with a 2-digit date is passed toGuido van Rossum1998-08-251-2/+15
| | | | mktime() and such.
* New section header style.Fred Drake1998-08-101-1/+2
| | | | Fix up a few synopses.
* Adjusted to use the new module synopsis support macros.Fred Drake1998-07-231-2/+4
|
* Added notes about epochs, the year 2038, and a small Y2K disclaimerGuido van Rossum1998-06-091-4/+19
| | | | | (all with index entries!). Also update the list of functions that take or yield a time represented as a 9-tuple.
* Added docs for strptime().Guido van Rossum1998-06-091-0/+12
|
* Lighten up tables.Fred Drake1998-04-111-1/+1
|
* Shift index entries around a little so the HTML doesn't have weird spacing.Fred Drake1998-04-111-10/+10
|
* Remove all uses of \sectcode; we can now use logical markup everywhere.Fred Drake1998-04-041-1/+1
|
* Minor nits.Fred Drake1998-04-031-59/+64
| | | | Lots of index entries.