Mercurial > cpython-lru_cache-weakref
changeset 86317:d513149e0c19 2.7
Refer to strftime(3) manpage for platform specific format codes.
Suggested by Skip Montanaro on docs@.
| author | Georg Brandl <georg@python.org> |
|---|---|
| date | Sun, 13 Oct 2013 18:28:25 +0200 |
| parents | 053eb1db0bf8 |
| children | fd2c34e0104b |
| files | Doc/library/datetime.rst Doc/library/time.rst |
| diffstat | 2 files changed, 6 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/Doc/library/datetime.rst Sun Oct 13 18:27:51 2013 +0300 +++ b/Doc/library/datetime.rst Sun Oct 13 18:28:25 2013 +0200 @@ -1603,7 +1603,8 @@ The full set of format codes supported varies across platforms, because Python calls the platform C library's :func:`strftime` function, and platform -variations are common. +variations are common. To see the full set of format codes supported on your +platform, consult the :manpage:`strftime(3)` documentation. The following is a list of all the format codes that the C standard (1989 version) requires, and these work on all platforms with a standard C
--- a/Doc/library/time.rst Sun Oct 13 18:27:51 2013 +0300 +++ b/Doc/library/time.rst Sun Oct 13 18:28:25 2013 +0200 @@ -350,8 +350,10 @@ >>> strftime("%a, %d %b %Y %H:%M:%S +0000", gmtime()) 'Thu, 28 Jun 2001 14:17:15 +0000' - Additional directives may be supported on certain platforms, but only the ones - listed here have a meaning standardized by ANSI C. + Additional directives may be supported on certain platforms, but only the + ones listed here have a meaning standardized by ANSI C. To see the full set + of format codes supported on your platform, consult the :manpage:`strftime(3)` + documentation. On some platforms, an optional field width and precision specification can immediately follow the initial ``'%'`` of a directive in the following order;