Floris Bruynooghe writes:
> One thing that they encountered and don't yet understand is that they
> reported issues with leaking filedescriptors. They used the bindings in
> a way where I expect it to only call notmuch_database_destroy() when
> they are done with it. From reading notmuch.h I
Hi Daniel,
On Tue 09 Jun 2020 at 09:19 -0400, Daniel Kahn Gillmor wrote:
> I see over on github that alot is trying to port to the notmuch2
> bindings, and having a few problems with it:
>
> https://github.com/pazz/alot/pull/1511
>
> alot is an important consumer of the notmuch python bindings,
This was released a while ago, we should support it.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Python 3.8 has been released for a while now, make sure we keep
supporting it correctly.
PyPy 3.6 wasn not configured correctly.
---
bindings/python-cffi/tox.ini | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/bindings/python-cffi/tox.ini b/bindings/python-cffi/tox.ini
Even though we use collections.abc.Set which implements all these
methods under their operator names, the actual named variations of
these methods are shockingly missing. So let's add them manually.
---
bindings/python-cffi/notmuch2/_tags.py | 21 +
This issue was found by alot's porting efforts. It seems these
were simply missing.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Since it is possible to use an atomic context to abort a number of
changes support this usage. Because the only way to actually abort
the transaction is to close the database this must also do so.
---
bindings/python-cffi/notmuch2/_database.py | 16 +++-
This is an implementation of what was suggested in
id:87v9k96xtl@powell.devork.be It closes the database as that is
the only safe way to do this afaik.
Currently when the database is closed there are still a bunch of
operations which can result in segfaults. Yet the API also promises
that
