diff options
| author | Georg Brandl <georg@python.org> | 2010-10-16 18:53:08 +0000 |
|---|---|---|
| committer | Georg Brandl <georg@python.org> | 2010-10-16 18:53:08 +0000 |
| commit | 573caa3476d93af707f4630ad1b9fc025347c391 (patch) | |
| tree | bff21ace1f6cd5f0f88ebba369a2e157a84bf360 /Doc/howto | |
| parent | 8e4ddcfaeae40ae0ef8609d31a19efd665f7b40d (diff) | |
| download | cpython-git-573caa3476d93af707f4630ad1b9fc025347c391.tar.gz | |
#10124: typo fix.
Diffstat (limited to 'Doc/howto')
| -rw-r--r-- | Doc/howto/cporting.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/cporting.rst b/Doc/howto/cporting.rst index 7cb0892abe..71844969b6 100644 --- a/Doc/howto/cporting.rst +++ b/Doc/howto/cporting.rst @@ -50,7 +50,7 @@ Python 3.0's :func:`str` (``PyString_*`` functions in C) type is equivalent to compatibility with 3.0, :c:type:`PyUnicode` should be used for textual data and :c:type:`PyBytes` for binary data. It's also important to remember that :c:type:`PyBytes` and :c:type:`PyUnicode` in 3.0 are not interchangeable like -:c:type:`PyString` and :c:type:`PyString` are in 2.x. The following example +:c:type:`PyString` and :c:type:`PyUnicode` are in 2.x. The following example shows best practices with regards to :c:type:`PyUnicode`, :c:type:`PyString`, and :c:type:`PyBytes`. :: |