traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarify the version information for the unicode() built-in. 

Closes SF bug #575272.
This commit is contained in:
Fred Drake 2002-06-29 16:06:47 +00:00
parent 1969817486
commit 78e057a32a
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Doc/lib/libfuncs.tex
View File

@ -873,13 +873,16 @@ def my_import(name):
behaviour of \code{str()} except that it returns Unicode strings
instead of 8-bit strings. More precisely, if \var{object} is an
Unicode string or subclass it will return a Unicode string without
any additional decoding applied. For objects which provide a
\code{__unicode__} method, it will call this method without
arguments to create a Unicode string. For all other objects, the
8-bit string version or representation is requested and then
converted to a Unicode string using the codec for the default
encoding in \code{'strict'} mode.
any additional decoding applied.
For objects which provide a \method{__unicode__()} method, it will
call this method without arguments to create a Unicode string. For
all other objects, the 8-bit string version or representation is
requested and then converted to a Unicode string using the codec for
the default encoding in \code{'strict'} mode.
\versionadded{2.0}
\versionchanged[Support for \method{__unicode__()} added]{2.2}
\end{funcdesc}
\begin{funcdesc}{vars}{\optional{object}}