Gmail eats Python

Jussi Piitulainen jpiitula at ling.helsinki.fi
Sat Jul 25 19:47:50 CEST 2015


Zachary Ware writes:

> On Jul 25, 2015 11:35 AM, "Laura Creighton" wrote:
>>
>> Gmail eats Python.
>>
>> We just saw this mail back from Sebastian Luque which says in part:
>>
>> >>> try: all_your_code_which_is_happy_with_non_scalars except
>> >>> WhateverErrorPythonGivesYouWhenYouTryThisWithScalars:
>> >>> whatever_you_want_to_do_when_this_happens
>>
>> Ow!  Gmail is understanding the >>> I stuck in as 'this is
>> from the python console as a quoting marker and thinks it can reflow
>> that.
>>
>> I think that splunqe must already have gmail set for plain text or
>> else even worse mangling must show up.
>>
>> How do you teach gmail not to reflow what it thinks of as
>> 'other people's quoted text'?
>
> Add same whitespace in front of the >'s, in plain text mode:
>
>    >>> def test(): pass
>    ...
>    >>> print('Hi world')
>    Hi world
>    >>>
>
> (Hopefully that will work from my phone)

Just in case anyone cares, Gnus shows me those indentations as octal
codes, \302\240\302\240 (followed by one ASCII space). I guess a
\302\240 is a NO-BREAK SPACE in UTF-8, and I guess Gnus does not know
this because there is no charset specification in the headers. That
seems to be missing whenever I see these codes instead of properly
rendered characters and bother to check the headers.

Has the world adopted UTF-8 as the default charset now or what? (I'll be
only glad to hear that it has, if it has, but a reference to some sort
of internet standard would be nice.)


More information about the Python-list mailing list