Re: [Python-Dev] [Python-checkins] r87504 - in python/branches/py3k: Doc/c-api/exceptions.rst Include/pyerrors.h Include/warnings.h
On Mon, 27 Dec 2010 02:49:27 +0100, victor.stinner
Author: victor.stinner Date: Mon Dec 27 02:49:26 2010 New Revision: 87504
Log: Issue #9738: Document encodings of error and warning functions
Modified: python/branches/py3k/Doc/c-api/exceptions.rst python/branches/py3k/Include/pyerrors.h python/branches/py3k/Include/warnings.h
Modified: python/branches/py3k/Doc/c-api/exceptions.rst ============================================================================== --- python/branches/py3k/Doc/c-api/exceptions.rst (original) +++ python/branches/py3k/Doc/c-api/exceptions.rst Mon Dec 27 02:49:26 2010 @@ -148,7 +148,8 @@ This function sets the error indicator and returns *NULL*. *exception* should be a Python exception class. The *format* and subsequent parameters help format the error message; they have the same meaning and - values as in :c:func:`PyUnicode_FromFormat`. + values as in :c:func:`PyUnicode_FromFormat`. *format* is an ASCII-encoding + string.
ASCII-encoded string, or ASCII encoding-string?
.. c:function:: int PyErr_WarnFormat(PyObject *category, Py_ssize_t stack_level, const char *format, ...)
Function similar to :c:func:`PyErr_WarnEx`, but use - :c:func:`PyUnicode_FromFormat` to format the warning message. + :c:func:`PyUnicode_FromFormat` to format the warning message. *format* is + an ASCII-encoded string.
So, the former, I'd guess :) -- R. David Murray www.bitdance.com
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
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. Victor
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
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
"Martin v. Löwis", 28.12.2010 11:40:
Le lundi 27 décembre 2010 à 23:07 -0500, R. David Murray a écrit :
ASCII-encoded string, or ASCII encoding-string?
[...] apparently, you would put the hyphen after if it's "encoding", and before if it's "encoded"; not sure why that is
I think David just put it there to point to the semantic difference. It's either a string that is "ASCII encoded", or an "encoding string" that refers to ASCII in some way. Whether you put a hyphen or not is a secondary concern. Stefan
Le mardi 28 décembre 2010 à 11:40 +0100, "Martin v. Löwis" a écrit :
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
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*".
Ooops, it's ASCII-encoded string (and not ASCII-encoding string): fixed by r87529. Victor
On Tue, 28 Dec 2010 13:58:24 +0100, Victor Stinner
Le mardi 28 décembre 2010 à 11:40 +0100, "Martin v. Löwis" a écrit :
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
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*".
Ooops, it's ASCII-encoded string (and not ASCII-encoding string): fixed by r87529.
Yes, exactly. Sorry for being a bit too subtle in my error report. -- R. David Murray www.bitdance.com
participants (4)
-
"Martin v. Löwis"
-
R. David Murray
-
Stefan Behnel
-
Victor Stinner