1 Return-Path: <teythoon@jade-hamburg.de>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 92C7440F45E
\r
6 for <notmuch@notmuchmail.org>; Sun, 8 Jan 2012 06:04:55 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Date"
\r
12 X-Spam-Status: No, score=0.433 tagged_above=-999 required=5
\r
13 tests=[INVALID_DATE=0.432, UNPARSEABLE_RELAY=0.001] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id Q669vVk8Tfcn for <notmuch@notmuchmail.org>;
\r
17 Sun, 8 Jan 2012 06:04:55 -0800 (PST)
\r
18 Received: from mail.cryptobitch.de (cryptobitch.de [88.198.7.68])
\r
19 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id E178640F45B
\r
22 for <notmuch@notmuchmail.org>; Sun, 8 Jan 2012 06:04:54 -0800 (PST)
\r
23 Received: from mail.jade-hamburg.de (unknown [85.183.11.228])
\r
24 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
\r
25 (No client certificate requested)
\r
26 by mail.cryptobitch.de (Postfix) with ESMTPSA id D7C5535A01E
\r
27 for <notmuch@notmuchmail.org>; Sun, 8 Jan 2012 15:04:52 +0100 (CET)
\r
28 Received: by mail.jade-hamburg.de (Postfix, from userid 401)
\r
29 id 3356CDF2A2; Sun, 8 Jan 2012 15:04:52 +0100 (CET)
\r
30 Received: from thinkbox.jade-hamburg.de (unknown
\r
31 [IPv6:fe80::216:d3ff:fe3e:5058%br0])
\r
32 (using TLSv1 with cipher AES256-SHA (256/256 bits))
\r
33 (No client certificate requested) (Authenticated sender: teythoon)
\r
34 by mail.jade-hamburg.de (Postfix) with ESMTPSA id 78645DF2A0;
\r
35 Sun, 8 Jan 2012 15:04:46 +0100 (CET)
\r
36 Received: from teythoon by thinkbox.jade-hamburg.de with local (Exim 4.77)
\r
37 (envelope-from <teythoon@thinkbox.jade-hamburg.de>)
\r
38 id 1RjtMa-0007sn-BK; Sun, 08 Jan 2012 15:04:44 +0100
\r
39 Content-Type: text/plain; charset="utf-8"
\r
41 Content-Transfer-Encoding: quoted-printable
\r
42 From: Justus Winter <4winter@informatik.uni-hamburg.de>
\r
43 To: Tomi Ollila <tomi.ollila@iki.fi>, Sebastian Spaeth <Sebastian@SSpaeth.de>,
\r
44 notmuch@notmuchmail.org
\r
46 <1323860305-15802-1-git-send-email-4winter@informatik.uni-hamburg.de>
\r
47 <1323860305-15802-6-git-send-email-4winter@informatik.uni-hamburg.de>
\r
48 <87hb0ekudt.fsf@SSpaeth.de> <yf6sjjvxrxs.fsf@taco2.nixu.fi>
\r
49 In-Reply-To: <yf6sjjvxrxs.fsf@taco2.nixu.fi>
\r
50 Date: Sun, 08 Jan 2012 14:04:44 -0000
\r
51 Message-ID: <20120108140444.26863.68188@thinkbox.jade-hamburg.de>
\r
52 Subject: Re: [PATCH 5/7] py3k: the basestring and unicode types are removed in
\r
54 Date: Sun, 08 Jan 2012 15:04:44 +0100
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Sun, 08 Jan 2012 14:04:55 -0000
\r
69 Hi Tomi, Hi Sebastian :)
\r
71 Quoting Tomi Ollila (2012-01-04 19:07:11)
\r
72 >On Mon, 02 Jan 2012 16:15:58 +0100, Sebastian Spaeth <Sebastian@SSpaeth.de=
\r
74 >> Happy new year. Pushed patches 1-4 of this series so far. Looking fine,
\r
78 >> but ugh, the below seems like a rather ugly hack in a function that is
\r
79 >> probably called quite often.
\r
81 >> Isn't there a more pretty variant avoiding these sys.version_info checks
\r
82 >> all over the place?
\r
84 Well, I rebased and updated this patch. There are now two different
\r
85 implementations of _str like there are two Python3StringMixIn
\r
86 classes. I'll send this patch as reply to this message.
\r
88 >Does the Python3StringMixIn stuff in later patches already handle this
\r
89 >patch -- and making this obsolete ?
\r
91 No, that only handles the __str__ and __unicode__ stuff.
\r