[Python-checkins] cpython (2.7): s/:c:type:/:ctype:/g

[ezio.melotti]

http://hg.python.org/cpython/rev/443d96cb48b5
changeset:   74068:443d96cb48b5
branch:      2.7
user:        Ezio Melotti <ezio.melotti at gmail.com>
date:        Mon Dec 19 07:17:08 2011 +0200
summary:
  s/:c:type:/:ctype:/g

files:
  Doc/c-api/unicode.rst |  6 +++---
  1 files changed, 3 insertions(+), 3 deletions(-)


diff --git a/Doc/c-api/unicode.rst b/Doc/c-api/unicode.rst
--- a/Doc/c-api/unicode.rst
+++ b/Doc/c-api/unicode.rst
@@ -328,8 +328,8 @@
 .. cfunction:: Py_UNICODE* PyUnicode_AsUnicode(PyObject *unicode)
 
    Return a read-only pointer to the Unicode object's internal
-   :c:type:`Py_UNICODE` buffer, *NULL* if *unicode* is not a Unicode object.
-   Note that the resulting :c:type:`Py_UNICODE*` string may contain embedded
+   :ctype:`Py_UNICODE` buffer, *NULL* if *unicode* is not a Unicode object.
+   Note that the resulting :ctype:`Py_UNICODE*` string may contain embedded
    null characters, which would cause the string to be truncated when used in
    most C functions.
 
@@ -394,7 +394,7 @@
    copied or -1 in case of an error.  Note that the resulting :ctype:`wchar_t`
    string may or may not be 0-terminated.  It is the responsibility of the caller
    to make sure that the :ctype:`wchar_t` string is 0-terminated in case this is
-   required by the application. Also, note that the :c:type:`wchar_t*` string
+   required by the application. Also, note that the :ctype:`wchar_t*` string
    might contain null characters, which would cause the string to be truncated
    when used with most C functions.
 

-- 
Repository URL: http://hg.python.org/cpython