A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-December/107050.html below:

[Python-Dev] [Python-checkins] r87504 - in python/branches/py3k: Doc/c-api/exceptions.rst Include/pyerrors.h Include/warnings.h

[Python-Dev] [Python-checkins] r87504 - in python/branches/py3k: Doc/c-api/exceptions.rst Include/pyerrors.h Include/warnings.h"Martin v. Löwis" martin at v.loewis.de
Tue Dec 28 11:40:01 CET 2010
Am 28.12.2010 11:28, schrieb Victor Stinner:
> Le lundi 27 décembre 2010 à 23:07 -0500, R. David Murray a écrit :
>> On Mon, 27 Dec 2010 02:49:27 +0100, victor.stinner <python-checkins at python.org> wrote:
>>> Author: victor.stinner
>>> Date: Mon Dec 27 02:49:26 2010
>>> New Revision: 87504
>>>
>>> Log:
>>> Issue #9738: Document encodings of error and warning functions
> 
>> ASCII-encoded string, or ASCII encoding-string?
> 
> Oh, I don't really care. Which one do you prefer? I used "ASCII-encoded
> string" and "UTF-8 encoded string", because "UTF-8-encoded" has too many
> "-". I should maybe be uniformized.

David's other concern was whether it should be "encod*ed*" or
"encod*ing*". It seems he would prefer "encoded". Not sure what
he would prefer wrt. hyphens (but apparently, you would put
the hyphen after if it's "encoding", and before if it's "encoded";
not sure why that is).

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4