From: "Rollins, Jameson" <jrollins@caltech.edu>
To: David Bremner <david@tethera.net>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Floris Bruynooghe <flub@devork.be>,
"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: segfault using python bindings
Date: Thu, 22 Aug 2019 19:37:34 +0000 [thread overview]
Message-ID: <87zhk1gfeq.fsf@caltech.edu> (raw)
In-Reply-To: <87ef1dgg1a.fsf@tethera.net>
On Thu, Aug 22 2019, David Bremner <david@tethera.net> wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>> (i also find "notmuch2" rather unsatisfying, but python doesn't have a
>> meaningful versioning system for backwards-incompatible API changes for
>> its modules, so this kind of name augmentation is the only strategy i'm
>> aware of).
>
> Naming is hard. What about "notmuch3" to hint that it's for python3? A
> transition plan could be to have notmuch load the new bindings, after a
> deprecation period.
Ug, this naming issue is unfortunate. I don't really like "notmuch3" as
a reference to python 3, honestly.
What about making these new bindings only for python3, and the old ones
relegating to python2, and then just using the same name? Is that too
confusing? Do we need to maintain both concurrently?
jamie.
next prev parent reply other threads:[~2019-08-22 19:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 14:49 segfault using python bindings David Čepelík
2018-11-11 20:16 ` David Bremner
2018-11-11 20:21 ` Gaute Hope
2018-11-15 21:13 ` Floris Bruynooghe
2018-11-16 4:44 ` Brian May
2018-11-16 10:29 ` David Bremner
2018-11-16 21:39 ` Floris Bruynooghe
2018-11-17 0:15 ` David Bremner
2018-11-16 10:27 ` David Bremner
2018-11-16 12:15 ` Daniel Kahn Gillmor
2018-11-16 22:07 ` Floris Bruynooghe
2019-08-14 19:20 ` David Bremner
2019-08-15 9:53 ` Floris Bruynooghe
2019-08-15 12:28 ` David Bremner
2019-08-20 17:20 ` Floris Bruynooghe
2019-08-21 16:02 ` Daniel Kahn Gillmor
2019-08-22 19:24 ` David Bremner
2019-08-22 19:37 ` Rollins, Jameson [this message]
2019-08-23 0:09 ` David Bremner
2019-08-23 1:59 ` Daniel Kahn Gillmor
2019-08-23 12:07 ` David Bremner
2019-08-23 20:43 ` Daniel Kahn Gillmor
2019-08-23 22:58 ` Rollins, Jameson
2019-08-26 17:09 ` Floris Bruynooghe
2019-08-26 17:28 ` David Bremner
2018-11-18 20:22 ` Dirk Van Haerenborgh
2018-11-18 23:34 ` David Bremner
2018-11-19 9:09 ` Dirk Van Haerenborgh
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=87zhk1gfeq.fsf@caltech.edu \
--to=jrollins@caltech.edu \
--cc=david@tethera.net \
--cc=dkg@fifthhorseman.net \
--cc=flub@devork.be \
--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).