notmuch/bindings/python-cffi/tests, branch 0.38.2

test: increase cffi timeout

2022-08-16T07:29:39Z

By default, the test suite uses 2min for other tests and 5s for cffi tests. Sporadically, this leads to test failures caused by the timeout on slower or loaded test infrastructure (as seen on ppc64le in Fedora's infrastructure during branch time). Increase the cffi timeout to the same 2m=120s. Signed-off-by: Michael J Gruber

python-cffi: use config_pairs API in ConfigIterator

2022-02-17T01:57:22Z

This returns all of the config keys with non-empty values, not just those that happen to be stored in the database.

Merge tag '0.34.3'

2022-01-09T23:34:58Z

notmuch 0.34.3 release

bindings/python-cffi: search for config by default

2022-01-09T19:16:51Z

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 objects

2022-01-01T15:48:40Z

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_string

2021-12-05T12:53:39Z

The python exception class was incorrectly loading the error message which resulted in unprintable exception objects.

lib: introduce notmuch_database_create_with_config

2021-02-06T23:48:34Z

This takes a config path parameter, and can use that to decide the new database location.

Fix typos

2020-08-10T00:14:36Z

Support aborting the atomic context

2020-06-16T11:17:39Z

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 owned

2020-06-16T11:02:02Z

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.