Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Jussi Piitulainen Newsgroups: comp.lang.python Subject: Re: Gmail eats Python Date: Sat, 25 Jul 2015 20:47:50 +0300 Organization: A noiseless patient Spider Lines: 42 Message-ID: References: <201507251634.t6PGYUvo028820@fido.openend.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="305c68510616a2e7ac08bcd2ff1598bd"; logging-data="10958"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19AIiEJfipuUKcBVLAaCTkdsC06zI6ZjKw=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:bkot61FhbmC4R1vxPsADcnU1mGY= sha1:3v2F2l3OQRtp1W0IaTJK3p7QSuE= Xref: csiph.com comp.lang.python:94567 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.)