On Fri 2019-08-23 09:07:12 -0300, David Bremner wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
>
>> The other possibility would be to implement the old "notmuch" API on top
>> of the new one with explicitly logged deprecations. But iirc, the
>> semantics and object lifecycle/ownership issues are subtly different
>> enough that this would be a non-trivial project.  I'd be happy to be
>> wrong though, perhaps someone closer to the systems (someone actively
>> using the current python bindings on an ongoing project?) could look
>> more closely?
>
> IIUC, it is precisely this compatibility layer that has stalled things
> for a year or so. I don't think we can afford to wait longer.

that matches my understanding too.  i'd love to move forward with the
improved bindings, under a different name.

if someone later figures out the compatibility layer that allows
implementation of the traditional "notmuch" module api atop the
notmuch2(?)  module, then we can always reclaim the name.

         --dkg