Changes between Version 1 and Version 2 of UnicodeEncodeError

Timestamp:

Mar 2, 2007, 1:57:35 PM (17 years ago)

Author:

Christian Boos

Comment:

make the "python interactive session" blocks narrower

UnicodeEncodeError

@@ -3 +3 @@
 It means that a given `unicode` object (i.e. the Python internal representation for a sequence of internationalized characters conforming to the Unicode standard) failed to be converted to a `str` object (i.e. a sequence of bytes). The failure means that there was a character which couldn't be represented by an appropriate sequence of bytes in the chosen output encoding.
 
-In practice, the default conversion being a "strict" one using the default encoding, which is 'ascii' most of the time, as soon as the `unicode` object contains characters outside of the ASCII range of characters (codepoint 0 to 127), the error will happen.
+In practice, the default conversion being a "strict" one using the default encoding, which is 'ascii' most of the time, the error will happen as soon as the `unicode` object contains characters outside of the ASCII range of characters (codepoint 0 to 127).
 
 This error was frequently seen during the transition to internal use of `unicode` that happened in Trac [milestone:0.10], and can still be seen now and then with Trac plugins that are not using the Trac API the way they should.
@@ -13 +13 @@
 Traceback (most recent call last):
   File "<stdin>", line 1, in ?
-UnicodeEncodeError: 'ascii' codec can't encode character u'\xee' in position 3: ordinal not in range(128)
+UnicodeEncodeError: 'ascii' codec can't encode character u'\xee'
+                    in position 3: ordinal not in range(128)
 >>> 
 }}}
@@ -22 +23 @@
 Traceback (most recent call last):
   File "<stdin>", line 1, in ?
-UnicodeEncodeError: 'ascii' codec can't encode character u'\xee' in position 3: ordinal not in range(128)
+UnicodeEncodeError: 'ascii' codec can't encode character u'\xee' 
+                    in position 3: ordinal not in range(128)
 }}}