notmuch/bindings/python-cffi/tests, branch 0.35thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.352022-01-09T23:34:58ZMerge tag '0.34.3'2022-01-09T23:34:58ZDavid Bremnerdavid@tethera.net2022-01-09T23:34:58Zurn:sha1:63d3b2b5cf8702b5fecea77392ce46f8a8249175
notmuch 0.34.3 release
bindings/python-cffi: search for config by default2022-01-09T19:16:51ZDavid Bremnerdavid@tethera.net2022-01-08T21:21:43Zurn:sha1:8b737af28bc377db3e661a5744f3b7479b7ce485
The previous (pre-0.34.2) constructor searched for a config file but
only if the database path was not specified, and only to retrieve
database.path. Neither of the available options (CONFIG.SEARCH or
CONFIG.NONE) matches this semantics exactly, but CONFIG.SEARCH causes
less breakage for people who relied on the old behaviour to set their
database.path [1]. Since it also seems like the friendlier option in
the long run, this commit switches to CONFIG.SEARCH as default.
This requires a certain amount of updating the pytest tests, but most
users will actually have a config file, unlike the test environment.
[1]: id:87fsqijx7u.fsf@metapensiero.it
bindings/python-cffi: add matched property to message objects2022-01-01T15:48:40ZDavid Bremnerdavid@tethera.net2022-01-01T14:36:43Zurn:sha1:9cc026f3daaa7731527787f8c7e729c0a08c456c
Existing users of the legacy python bindings use
message.get_flags(Message.FLAG.MATCH) to determine which messages in a
thread matched. Since the bindings don't provide get_flags anymore,
they should provide a property analogous to the existing "excluded"
property.
Fix error message when using notmuch_status_to_string2021-12-05T12:53:39ZFloris Bruynoogheflub@devork.be2021-11-06T11:02:37Zurn:sha1:ca4e1d885b0d9dcdeb45ad6f2829f88dafc7949c
The python exception class was incorrectly loading the error message
which resulted in unprintable exception objects.
lib: introduce notmuch_database_create_with_config2021-02-06T23:48:34ZDavid Bremnerdavid@tethera.net2021-01-02T00:43:14Zurn:sha1:ac67cd84eea1148680ab3a377d35ae346073f138
This takes a config path parameter, and can use that to decide the
new database location.
Fix typos2020-08-10T00:14:36ZJonas Bernoullijonas@bernoul.li2020-08-08T11:49:55Zurn:sha1:6c84dee53193a78cf797b44d3febcc14488ea6b1Support 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 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.
Add missing set methods to tagsets2020-06-15T10:14:11ZFloris Bruynoogheflub@devork.be2020-06-14T18:33:55Zurn:sha1:a00f3a1f7a646d9834a5de57a29cf3e900dbdcdf
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.