notmuch/bindings, branch debian/0.30-1thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.30-12020-07-11T01:21:19Zversion: set to 0.302020-07-11T01:21:19ZDavid Bremnerdavid@tethera.net2020-07-11T01:21:19Zurn:sha1:e56a207ce14386b3e826dd267c549427b2c3f9ecversion: bump to 0.30~rc32020-07-03T09:45:17ZDavid Bremnerdavid@tethera.net2020-07-03T09:45:17Zurn:sha1:038b3e7c302fed34b8734d3dcac2c5568d4147f3bindings/python-cffi: copy version file into bindings dir2020-07-03T09:38:55ZDavid Bremnerdavid@tethera.net2020-06-30T00:22:47Zurn:sha1:3a42abb456893b71b530f099a1467400f2b0ea71
Attempt to avoid breaking "pip install ."
As far as I can tell, we need to have a copy (not just a relative
symlink) of the version file.
python-cffi: read version from notmuch version file2020-06-19T10:01:13ZFloris Bruynoogheflub@devork.be2020-06-19T09:46:28Zurn:sha1:81057164cddf6a5c1d4c30a23767c4de8e615c1c
This keeps it in sync with the main notmuch version which is less
confusing to users.
version: update to 0.30~rc22020-06-16T11:29:39ZDavid Bremnerdavid@tethera.net2020-06-16T11:29:39Zurn:sha1:cda6e4d1046641871413710f3786c43697bd6d19Support 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.
python/notmuch2: do not destroy messages owned by a query2020-06-16T11:02:02ZAnton Khirnovanton@khirnov.net2020-06-15T20:58:49Zurn:sha1:131757907907380213b32934d9e73cec942ace43
Any messages retrieved from a query - either directly via
search_messages() or indirectly via thread objects - are owned by that
query. Retrieving the same message (i.e. corresponding to the same
message ID / database object) several times will always yield the same
C object.
The caller is allowed to destroy message objects owned by a query before
the query itself - which can save memory for long-lived queries.
However, that message must then never be retrieved again from that
query.
The python-notmuch2 bindings will currently destroy every message object
in Message._destroy(), which will lead to an invalid free if the same
message is then retrieved again. E.g. the following python program leads
to libtalloc abort()ing:
import notmuch2
db = notmuch2.Database(mode = notmuch2.Database.MODE.READ_ONLY)
t = next(db.threads('*'))
msgs = list(zip(t.toplevel(), t.toplevel()))
msgs = list(zip(t.toplevel(), t.toplevel()))
Fix this issue by creating a subclass of Message, which is used for
"standalone" message which have to be freed by the caller. Message class
is then used only for messages descended from a query, which do not need
to be freed by the caller.
python config access: fix style and KeyError bug2020-06-16T00:50:03ZFloris Bruynoogheflub@devork.be2020-06-15T21:55:53Zurn:sha1:1bca41698a03980b701558fb5c481ef0a340460d
This fixes some minor style/pep8 things and adds tests for the new
config support. Also fixes a bug where KeyError was never raised
on a missing key.
python/notmuch2: add bindings for the database config strings2020-06-16T00:50:03ZAnton Khirnovanton@khirnov.net2020-06-15T21:55:52Zurn:sha1:5a58754841f4d3e62d104ad338c8ca2c481dc32e