From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
Floris Bruynooghe <flub@devork.be>,
Ruben Pollan <meskio@sindominio.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] python: add bindings for notmuch_message_get_propert(y/ies)
Date: Thu, 30 Nov 2017 09:19:57 -0500 [thread overview]
Message-ID: <87mv334zn6.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87efofdgp8.fsf@tesseract.cs.unb.ca>
On Thu 2017-11-30 09:44:19 -0400, David Bremner wrote:
> Floris Bruynooghe <flub@devork.be> 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.
Agreed, my reading of the source is that we expect strings for both
property names and property values. If they're both strings, we should
not support anything other than UTF-8 in either case.
--dkg
prev parent reply other threads:[~2017-11-30 14:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 22:29 [PATCH] python: add bindings for notmuch_message_get_property Ruben Pollan
2017-11-15 22:48 ` meskio
2017-11-17 9:03 ` Daniel Kahn Gillmor
2017-11-28 22:46 ` [PATCH] python: add bindings for notmuch_message_get_propert(y/ies) Ruben Pollan
2017-11-28 22:51 ` meskio
2017-11-29 1:57 ` Daniel Kahn Gillmor
2017-11-29 8:02 ` meskio
2017-11-29 8:03 ` Ruben Pollan
2017-12-23 15:59 ` David Bremner
2018-04-27 19:12 ` meskio
2018-04-27 19:15 ` Ruben Pollan
2018-05-01 13:06 ` David Bremner
2018-05-01 15:24 ` meskio
2018-05-01 15:28 ` Ruben Pollan
2018-05-02 0:08 ` David Bremner
2018-05-02 17:00 ` meskio
2018-05-02 17:01 ` Ruben Pollan
2018-05-02 23:50 ` David Bremner
2017-11-29 21:40 ` Floris Bruynooghe
2017-11-30 13:44 ` David Bremner
2017-11-30 14:19 ` Daniel Kahn Gillmor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv334zn6.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=flub@devork.be \
--cc=meskio@sindominio.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).