提交 353b0fc9 authored 作者: Frédéric Bastien's avatar Frédéric Bastien

Merge pull request #3846 from kmike/patch-1

DOC removed incorrect statement from compatibility docs
...@@ -92,8 +92,7 @@ come up for Theano's purposes. ``str`` represents encoded text, i.e. character ...@@ -92,8 +92,7 @@ come up for Theano's purposes. ``str`` represents encoded text, i.e. character
encoding-aware; all Python 3 strings are internally stored as Unicode. When encoding-aware; all Python 3 strings are internally stored as Unicode. When
converting from one or the other, you must `.encode(...)` bytes and converting from one or the other, you must `.encode(...)` bytes and
`.decode(...)` strings with a given character encoding (e.g. ``'ascii'``, `.decode(...)` strings with a given character encoding (e.g. ``'ascii'``,
``'utf8'``, ``'latin1'``). Fortunately, these methods exist as no-ops ``'utf8'``, ``'latin1'``).
in Python 2.6 and 2.7.
C code compatibility C code compatibility
-------------------- --------------------
......
Markdown 格式
0%
您添加了 0 到此讨论。请谨慎行事。
请先完成此评论的编辑!
注册 或者 后发表评论