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-01.23:18:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.
Date User Action Args
2014-12-01 23:18:03belopolskysetrecipients: + belopolsky, cvrebert, docs@python, akira
2014-12-01 23:18:03belopolskysetmessageid: <>
2014-12-01 23:18:03belopolskylinkissue22356 messages
2014-12-01 23:18:03belopolskycreate