When refering to Unicode characters in exception messages and
docstrings, the documentation guidelines call for "Unicode", not
"unicode". Comply.
diff --git a/Python/bltinmodule.c b/Python/bltinmodule.c
index 84d7aeb..8b8bf3d 100644
--- a/Python/bltinmodule.c
+++ b/Python/bltinmodule.c
@@ -192,7 +192,7 @@
static char unicode_doc[] =
"unicode(string [, encoding[, errors]]) -> object\n\
\n\
-Creates a new unicode object from the given encoded string.\n\
+Creates a new Unicode object from the given encoded string.\n\
encoding defaults to 'utf-8' and errors, defining the error handling,\n\
to 'strict'.";
@@ -368,9 +368,9 @@
}
static char unichr_doc[] =
-"unichr(i) -> unicode character\n\
+"unichr(i) -> Unicode character\n\
\n\
-Return a unicode string of one character with ordinal i; 0 <= i < 65536.";
+Return a Unicode string of one character with ordinal i; 0 <= i < 65536.";
static PyObject *
@@ -1657,7 +1657,7 @@
ord = (long)*PyUnicode_AS_UNICODE(obj);
} else {
PyErr_Format(PyExc_TypeError,
- "expected string or unicode character, " \
+ "expected string or Unicode character, " \
"%.200s found", obj->ob_type->tp_name);
return NULL;
}
@@ -1673,7 +1673,7 @@
static char ord_doc[] =
"ord(c) -> integer\n\
\n\
-Return the integer ordinal of a one character [unicode] string.";
+Return the integer ordinal of a one character string.";
static PyObject *