Re: segfault using python bindings

Subject: Re: segfault using python bindings

Date: Wed, 21 Aug 2019 12:02:15 -0400

To: Floris Bruynooghe, David Bremner,


From: Daniel Kahn Gillmor

On Tue 2019-08-20 19:20:30 +0200, Floris Bruynooghe wrote:
> Sounds reasonable, just a quick note that I'm on holiday at the moment
> and generally won't be too quick.  But I guess there's no rush.  I was
> also trying to improve the docs but got sidetracked at some point.
> There should be already reasonable good docstrings though.

thanks for having done all this work already!

> For path series what did you have in mind?  One single patch with the
> whole lot?  The original history at https:://github/flub/notdb?
> Something in between?

I would be happy with a series of patches, but the cited github history
has only one commit in the first place :P

> I also recall some comments about the naming not being liked much
> (notdb).  I'm open to some bikeshedding on the naming if it bothers
> people.  I was only aiming for something short but under a different
> import name, which are probably still useful features to keep.

fwiw, "notdb" doesn't really resonate with me, but i wouldn't block you
if you decided to stick with it.

I'd generally prefer something like "notmuch2" because it makes it much
clearer that it is associated with notmuch, and that it is the successor
to the original notmuch bindings.

(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).

signature.asc (application/pgp-signature)
notmuch mailing list