From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 7530E6DE0191 for ; Thu, 30 Nov 2017 05:44:27 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qimB3P7xlIWA for ; Thu, 30 Nov 2017 05:44:26 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 2EDFF6DE00C4 for ; Thu, 30 Nov 2017 05:44:26 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1eKP8Y-00083M-FA; Thu, 30 Nov 2017 08:44:22 -0500 Received: (nullmailer pid 27692 invoked by uid 1000); Thu, 30 Nov 2017 13:44:19 -0000 From: David Bremner To: Floris Bruynooghe , Daniel Kahn Gillmor , Ruben Pollan , notmuch@notmuchmail.org Subject: Re: [PATCH] python: add bindings for notmuch_message_get_propert(y/ies) In-Reply-To: <87tvxcepc0.fsf@devork.be> References: <878tf5uvjm.fsf@fifthhorseman.net> <20171128224611.10712-1-meskio@sindominio.net> <87k1y97sor.fsf@fifthhorseman.net> <87tvxcepc0.fsf@devork.be> Date: Thu, 30 Nov 2017 09:44:19 -0400 Message-ID: <87efofdgp8.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 13:44:27 -0000 Floris Bruynooghe writes: > Daniel Kahn Gillmor writes: > > This also has the binary question problem, is this returned as bytes or > as str? Current Python bindings seem to go for .decode('utf-8', > errors='ignore') afaik which is somewhat lossy. > IMHO there's no reason to support non-utf8 properties. We should document this restriction now while adoption is relatively light. d