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 belopolsky
Recipients akira, belopolsky, cvrebert, docs@python
Date 2014-12-02.00:38:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I've provide the direct quote from *C* standard ...

I understand that C standard uses the word "encoding", but it does so for a reason that is completely unrelated to the choice of epoch.  "Encoding" is how the bytes in memory should be interpreted as "number of seconds" or some other notion of time.  For, example "two's complement little-endian 32-bit signed int" is an example of valid time_t encoding, another example would be IEEE 754 big-endian 64-bit double.  Note that these choices are valid for both C and POSIX standards.

If you google for your phrase "time in POSIX encoding", this issue is the only hit.  This strongly suggests that your choice of words is not the most natural.
Date User Action Args
2014-12-02 00:38:57belopolskysetrecipients: + belopolsky, cvrebert, docs@python, akira
2014-12-02 00:38:57belopolskysetmessageid: <>
2014-12-02 00:38:57belopolskylinkissue22356 messages
2014-12-02 00:38:57belopolskycreate