notmuch/bindings/python-cffi/tests/test_database.py, branch 0.31.2thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.31.22020-06-16T11:17:39ZSupport aborting the atomic context2020-06-16T11:17:39ZFloris Bruynoogheflub@devork.be2020-06-14T15:23:19Zurn:sha1:776a54a0e437651abd69a03b9f7d591ea1f992cb
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.
Amended by db: Note the limitation requiring close is a limitation of
the underlying notmuch API, which should be fixed in a future notmuch
release.
Make messages returned by Thread objects owned2020-06-16T11:02:02ZFloris Bruynoogheflub@devork.be2020-06-15T20:58:50Zurn:sha1:2d895a0119b423b117d10e890c9e0eb5d2a9cdf8
This reverses the logic of StandaloneMessage to instead create a
OwnedMessage. Only the Thread class allows retrieving messages more
then once so it can explicitly create such messages.
The added test fails with SIGABRT without the fix for the message
re-use in threads being present.
Rename package to notmuch22019-12-03T12:12:30ZFloris Bruynoogheflub@devork.be2019-11-17T16:41:35Zurn:sha1:e2df30f7a98f91543d0b3561dbb366eb4b3d812c
This is based on a previous discussion on the list where this was more
or less seen as the least-bad option.
Introduce CFFI-based python bindings2019-12-03T12:12:30ZFloris Bruynoogheflub@google.com2019-10-08T21:03:12Zurn:sha1:83c2d158983875bf77a9b7662894df585b61741c
This introduces CFFI-based Python3-only bindings.
The bindings aim at:
- Better performance on pypy
- Easier to use Python-C interface
- More "pythonic"
- The API should not allow invalid operations
- Use native object protocol where possible
- Memory safety; whatever you do from python, it should not coredump.