Take 2 on mentioning the with statement, this time without inadvertently killing the Unicode examples

This commit is contained in:
Nick Coghlan 2006-04-23 16:35:19 +00:00
parent e0ea50bc3b
commit 09b1bc39e7
1 changed files with 5 additions and 3 deletions

View File

@ -941,9 +941,9 @@ with \function{str()}, conversion takes place using this default encoding.
u'abc'
>>> str(u"abc")
'abc'
>>> u"<EFBFBD>"
>>> u"äöü"
u'\xe4\xf6\xfc'
>>> str(u"<EFBFBD>")
>>> str(u"äöü")
Traceback (most recent call last):
File "<stdin>", line 1, in ?
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: ordinal not in range(128)
@ -955,7 +955,7 @@ that takes one argument, the name of the encoding. Lowercase names
for encodings are preferred.
\begin{verbatim}
>>> u"<EFBFBD>".encode('utf-8')
>>> u"äöü".encode('utf-8')
'\xc3\xa4\xc3\xb6\xc3\xbc'
\end{verbatim}
@ -3744,6 +3744,7 @@ In real world applications, the \keyword{finally} clause is useful
for releasing external resources (such as files or network connections),
regardless of whether the use of the resource was successful.
\section{Predefined Clean-up Actions \label{cleanup-with}}
Some objects define standard clean-up actions to be undertaken when
@ -3775,6 +3776,7 @@ even if a problem was encountered while processing the lines. Other
objects which provide predefined clean-up actions will indicate
this in their documentation.
\chapter{Classes \label{classes}}
Python's class mechanism adds classes to the language with a minimum