Feb. 18, 2012
11:37 p.m.
Ethan Furman wrote:
I can see confusion again creeping in when somebody (like myself ;) sees a datatype which seemingly supports a mixture of unicode and raw bytes only to find out that 'uni_raw(...)[5] != 32' because a u' ' was returned and an integer (or raw byte) was expected at that location.
I wasn't intending that an int would be returned when you index a non-char position. Indexing and slicing would always return another mixed-string object. -- Greg