Message 231964 - Python tracker

➜

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	<1417475883.55.0.627965515414.issue22356@psf.upfronthosting.co.za>
In-reply-to

Content
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 <http://pubs.opengroup.org/onlinepubs/9699919799/>, I get crypt - string encoding function (CRYPT) encrypt - encoding function (CRYPT) setkey - set encoding key (CRYPT) and nothing related to time.

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 <http://pubs.opengroup.org/onlinepubs/9699919799/>, I get

crypt - string encoding function (CRYPT) 
encrypt - encoding function (CRYPT) 
setkey - set encoding key (CRYPT)

and nothing related to time.

History
Date	User	Action	Args
2014-12-01 23:18:03	belopolsky	set	recipients: + belopolsky, cvrebert, docs@python, akira
2014-12-01 23:18:03	belopolsky	set	messageid: <1417475883.55.0.627965515414.issue22356@psf.upfronthosting.co.za>
2014-12-01 23:18:03	belopolsky	link	issue22356 messages
2014-12-01 23:18:03	belopolsky	create