* Tiago Saboga (Thu, 13 Dec 2007 17:05:55 -0200)
> On Thu, Dec 13, 2007 at 07:41:08AM -0500, Kent Johnson wrote:
> > Tiago Saboga wrote:
> >> : 'ascii' codec can't encode
> >> character u'\xe7' in position 2: ordinal not in range(128)
> >>
> >> ===
> >>
> >> What
Alan Gauld wrote:
> But I think Python itself is pretty safe with unicode v ascii in most
> cases.
I was actually holding my tongue on that one. My guess is it varies from
one module to the next depending on how well maintained they are, but
I don't really know.
> I'm sure Kent will be able
"Tiago Saboga" <[EMAIL PROTECTED]> wrote
> But in general, in the python libraries, I thought it would be safe
> to
> assume that one can equally send a string or a unicode object, and
> that otherwise there would be a warning in the docs. Is this
> assumption plain wrong, is this info really mis
On Thu, Dec 13, 2007 at 07:41:08AM -0500, Kent Johnson wrote:
> Tiago Saboga wrote:
>> : 'ascii' codec can't encode
>> character u'\xe7' in position 2: ordinal not in range(128)
>>
>> ===
>>
>> What's happening? Why do the readline methods accept a multibyte
>> s
Tiago Saboga wrote:
> : 'ascii' codec can't encode
> character u'\xe7' in position 2: ordinal not in range(128)
>
> ===
>
> What's happening? Why do the readline methods accept a multibyte
> string ('ação') but not a unicode (u'ação')?
I don't know what is hap
Hi,
I am facing what seems like a bug, and the docs are not enough to tell
me where the bug lies. In ipython, I can't type a multiline unicode
string. The bug is reported here [1], and the output is like that
(except that the commented out lines are modifications I have done):
===
