diff options
author | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-19 07:58:56 (GMT) |
---|---|---|
committer | Ezio Melotti <ezio.melotti@gmail.com> | 2011-10-19 07:58:56 (GMT) |
commit | e130a52d8a60229f53c8bc2ea7a1f51ee592bbd7 (patch) | |
tree | b7f128d5f626c78d57d53812a5953c6eb56cca72 /Doc/howto/pyporting.rst | |
parent | a5a9a9c3696af0a4a0df74618e63a4d47a62e00f (diff) | |
download | cpython-e130a52d8a60229f53c8bc2ea7a1f51ee592bbd7.zip cpython-e130a52d8a60229f53c8bc2ea7a1f51ee592bbd7.tar.gz cpython-e130a52d8a60229f53c8bc2ea7a1f51ee592bbd7.tar.bz2 |
Remove duplication.
Diffstat (limited to 'Doc/howto/pyporting.rst')
-rw-r--r-- | Doc/howto/pyporting.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/pyporting.rst b/Doc/howto/pyporting.rst index 124ef33..309f3f7 100644 --- a/Doc/howto/pyporting.rst +++ b/Doc/howto/pyporting.rst @@ -328,7 +328,7 @@ the bytes/string dichotomy. Because Python 2 allowed the ``str`` type to hold textual data, people have over the years been rather loose in their delineation of what ``str`` instances held text compared to bytes. In Python 3 you cannot be so care-free anymore and need to properly handle the difference. The key -handling this issue to to make sure that **every** string literal in your +handling this issue to make sure that **every** string literal in your Python 2 code is either syntactically of functionally marked as either bytes or text data. After this is done you then need to make sure your APIs are designed to either handle a specific type or made to be properly polymorphic. |