Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!newsfeed3.funet.fi!newsfeeds.funet.fi!news.cc.tut.fi!not-for-mail From: Anssi Saari Newsgroups: comp.lang.python Subject: Re: Python usage numbers Date: Wed, 15 Feb 2012 11:56:12 +0200 Lines: 22 Message-ID: References: <4F36E2F5.9000505@gmail.com> <4f37229b$0$29986$c3e8da3$5496439d@news.astraweb.com> NNTP-Posting-Host: 2001:708:310:3430:216:35ff:fe3e:dee7 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: news.cc.tut.fi 1329299772 3846 2001:708:310:3430:216:35ff:fe3e:dee7 (15 Feb 2012 09:56:12 GMT) X-Complaints-To: abuse@tut.fi NNTP-Posting-Date: Wed, 15 Feb 2012 09:56:12 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) Cancel-Lock: sha1:nW0R3JQvrU+zGkmzU0D0omp6m1I= Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:20434 Matej Cepl writes: > Slightly less flameish answer to the question “What should I do, > really?” is a tough one: all these suggested answers are bad because > they don’t deal with the fact, that your input data are obviously > broken. The rest is just pure GIGO … Well, sure, but it happens that input data is broken and not fixable. For example, I did a little program to display email headers like the old frm that was bundled with elm, only with support for MIME decoding of the headers. Obviously lots of email software is still completely broken regarding MIME and also multi-line headers. However, something useful can still be extracted from that broken data. > BTW, can you display the following line? > > Příliš žluťoučký kůň úpěl ďábelské ódy. Looks fine to me. You used an ellipsis too above. Well, I don't know what it shold look like exactly. Lots of accents. Hmm, Google says it means "The quick brown fox cried too lazy"? Seems appropriate :) BTW, I'm sending this via Usenet, I wonder what happens in the mail-news gateway?