notmuch/bindings/python-cffi/notmuch2, branch debian/0.39-1thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.39-12025-03-14T00:18:15Zbindings/python-cffi: fix docstring for message.header()2025-03-14T00:18:15ZMichael J Grubergit@grubix.eu2025-03-04T12:39:43Zurn:sha1:5802f5d6269172222a6fccf5908eae833014917b
The cffi bindings raise a LookupError in case a header is not present.
Adjust the docstring to say so.
The legacy bindings behaved differently, and this is one of the things
to be aware of when migrating to the cffi bindings.
python: Fix message ID docstring2025-02-28T15:31:55ZFloris Bruynoogheflub@devork.be2025-02-24T20:08:19Zurn:sha1:ed29a9c37ec382fc2d5b1d1ecc1f1fb28a6769c6
The messageidb attribute does not exist. The returned BinString type
already allows use as both strings and binary. Presumably this was
written before that type was adopted.
python: fix documentation typo2025-02-22T10:59:48ZDavid Bremnerdavid@tethera.net2025-02-15T19:27:51Zurn:sha1:9782c8651192c1496541bd8949b7991c41528b3f
The method is actually called 'getall'.
fix segfaults in Python cFFI API and add tests2025-02-07T16:13:16ZLars Kotthofflars@larsko.org2025-02-06T02:52:51Zurn:sha1:9c1f6cf746725af7bbbb66e746c5d694723ac0eb
Several iterators in the Python cFFI API destroyed the objects they iterated
over too early (when the iterator was exhausted), causing subsequent segfaults
in common cases like creating a list from the iterator. This patch fixes the
segfaults and add tests to ensure that they don't happen again.
bindings/python-cffi: fix docstring2022-07-05T10:34:25ZDavid Bremnerdavid@tethera.net2022-07-03T20:26:46Zurn:sha1:db44af75ad5a79b3fd5ecad93fe95195ef175ebd
the method Database.get_message does exist any more (if it ever
did). This makes the docstring unhelpful as an example.
lib: add NOTMUCH_STATUS_CLOSED_DATABASE, use in _n_d_ensure_writable2022-06-25T19:06:18ZDavid Bremnerdavid@tethera.net2022-05-25T10:51:16Zurn:sha1:3f27cce71f9f154cb0c2134c32d41c31eb62a239
In order for a database to actually be writeable, it must be the case that it
is open, not just the correct type of Xapian object. By explicitely
checking, we are able to provide better error reporting, in particular
for the previously broken test in T566-lib-message.
python-cffi: use config_pairs API in ConfigIterator2022-02-17T01:57:22ZDavid Bremnerdavid@tethera.net2022-02-09T12:28:54Zurn:sha1:9ddd13f75827f4972872c8766320c7cb80b1819b
This returns all of the config keys with non-empty values, not just
those that happen to be stored in the database.
lib/open: no default mail root in split configurations2022-01-15T19:59:39ZDavid Bremnerdavid@tethera.net2021-12-25T13:33:05Zurn:sha1:fad2e7540bf9309bfb335650ded753e9ed085eff
If we know the configuration is split, but there is no mail root
defined, this indicates a (lack of) configuration error. Currently
this can only arise in XDG configurations.
Merge 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