This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author akira
Recipients akira, belopolsky, cvrebert, docs@python
Date 2014-12-01.23:33:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <> (Alexander Belopolsky's message of "Mon, 01 Dec 2014 23:18:03 +0000")
> Alexander Belopolsky added the comment:
> In the context of Python library documentation, the word "encoding"
> strongly suggests that you are dealing with string/bytes.  The
> situation may be different in C. If you want to refer to something
> that is defined by the POSIX standard you should use the words that
> can actually be found in that standard.
> When I search for "encoding" at <>, I get
> crypt - string encoding function (CRYPT) 
> encrypt - encoding function (CRYPT) 
> setkey - set encoding key (CRYPT)
> and nothing related to time.

I've provide the direct quote from *C* standard in my previous message msg231957:

  > 2. What is "calendar time in POSIX encoding"? This sounds like what time.asctime() returns.

  It is the language used by C standard for time() function:

    The time function determines the current calendar time. The encoding
    of the value is unspecified.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ <- from the C standard

notice the word *encoding* in the quote.
Date User Action Args
2014-12-01 23:33:35akirasetrecipients: + akira, belopolsky, cvrebert, docs@python
2014-12-01 23:33:35akiralinkissue22356 messages
2014-12-01 23:33:35akiracreate